CVE-2026-107593

waiting for further signalsZero needs more public information before it can validate it.

GHSA-7gv5-qqq4-jvp4 ↗EUVD-2026-132700 ↗

no check availablenot proven exploitable
cve.orgpublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).kevAttacks confirmed in the real world.
Mooberry Book Manager <= 4.16.2
ETK-2026-5184Zero's internal tracking ID, independent of the CVE number., permanent identifier
15h 13msince last run
31mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = trigger signal
trigger signal (cve.org) +0hwaiting for further signals+2h34m
0
+2h
+4h
+6h
+8h
+10h
+12h

description

Mooberry Book Manager through 4.16.2 has an AJAX action that does not adequately enforce user permissions. An authenticated user, including a subscriber-level account, can change stored book purchase links and a related plugin setting.

mitigation

Restrict untrusted user accounts and deactivate the plugin where its book-link features are not needed. Apply a vendor release that corrects the authorization check when one is confirmed.

check
no
exploit
no
automationDeterministic: a check that runs on its own, the same request on every target. Contextual: an agentic technique that needs to be applied per target, for bugs that depend on contextual flows.
contextual
auth requiredWhether an attacker needs an account first, based on the CVSS vector's Privileges Required.
–
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
–
agent run time
31m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-11-22 06:00Z
Δ to public pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).
–
Δ to kevAttacks confirmed in the real world.
–

outcome

Contextual, not validated: no deterministic check could cover this one, and no technique passed our review.

source signals

Public signals that triggered or updated the pipeline. These are inputs for the deltas above.

  1. 2026-11-22 06:00Z
    ghsa: trigger signal, started the run
  2. 2026-11-22 06:00Z

this entry in the feed

GET /api/v1/feed/CVE-2026-107593

{
  "etk_id": "ETK-2026-5184",
  "cve_id": "CVE-2026-107593",
  "display_id": "CVE-2026-107593",
  "ghsa_id": "GHSA-7gv5-qqq4-jvp4",
  "euvd_id": "EUVD-2026-132700",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Missing authorization in Mooberry Book Manager AJAX action",
  "summary": "Mooberry Book Manager through 4.16.2 has an AJAX action that does not adequately enforce user permissions. An authenticated user, including a subscriber-level account, can change stored book purchase links and a related plugin setting.",
  "mitigation": "Restrict untrusted user accounts and deactivate the plugin where its book-link features are not needed. Apply a vendor release that corrects the authorization check when one is confirmed.",
  "vendor": null,
  "product": "Mooberry Book Manager",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 0, <= 4.16.2"
      ],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "Mooberry Book Manager",
      "purl": null
    }
  ],
  "cwes": null,
  "cvss_score": null,
  "cvss_src": null,
  "cvss_vector": null,
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 31.2574734,
  "t0_at": "2026-11-22T06:00:07.444000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-11-22T06:00:07.444000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-11-22T06:00:07.444000+00:00",
      "url": "https://github.com/advisories/GHSA-7gv5-qqq4-jvp4"
    }
  }
}

published 2026-11-22 08:03Z
last change 2026-11-22 18:21Z

Need the technical details behind an entry?

Every entry here shows what we attempted and when. The technical details, the generated exploit that fired it and the evidence behind the verdict are not public. Tell us about your use case and we’ll get back to you about extended API access.