CVE-2026-132081

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

GHSA-gmh6-mmrh-jf9j ↗EUVD-2026-131952 ↗

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.
Titan Anti-spam & Security < 7.5.5
fixed in 7.5.5
ETK-2026-5112Zero's internal tracking ID, independent of the CVE number., permanent identifier
2h 22msince last run
30mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = trigger signal
trigger signal (cve.org) +0hwaiting for further signals+1h26m
0
+2h
+4h
+6h
+8h
+10h
+12h

description

Titan Anti-spam & Security for WordPress versions before 7.5.5 can leave log-export archives accessible from the uploads directory. An unauthenticated attacker may obtain diagnostic data, including visitor IP addresses and site system information, after an administrator performs a log export.

mitigation

Update Titan Anti-spam & Security to version 7.5.5 or later. Remove any previously generated diagnostic archives from the WordPress uploads directory.

fixed in 7.5.5

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.
–
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
30m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-11-21 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

No artifact: an exploit or check was attempted but could not be produced at this moment.

source signals

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

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

this entry in the feed

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

{
  "etk_id": "ETK-2026-5112",
  "cve_id": "CVE-2026-132081",
  "display_id": "CVE-2026-132081",
  "ghsa_id": "GHSA-gmh6-mmrh-jf9j",
  "euvd_id": "EUVD-2026-131952",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Public diagnostic archives in Titan Anti-spam & Security",
  "summary": "Titan Anti-spam & Security for WordPress versions before 7.5.5 can leave log-export archives accessible from the uploads directory. An unauthenticated attacker may obtain diagnostic data, including visitor IP addresses and site system information, after an administrator performs a log export.",
  "mitigation": "Update Titan Anti-spam & Security to version 7.5.5 or later. Remove any previously generated diagnostic archives from the WordPress uploads directory.",
  "vendor": null,
  "product": "Titan Anti-spam & Security",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 0, < 7.5.5"
      ],
      "ecosystem": null,
      "fixed_versions": [
        "7.5.5"
      ],
      "package_name": "Titan Anti-spam & Security",
      "purl": null
    }
  ],
  "cwes": null,
  "cvss_score": null,
  "cvss_src": null,
  "cvss_vector": null,
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "deterministic",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 30.006385883333333,
  "t0_at": "2026-11-21T06:00:12.085000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-11-21T06:00:12.085000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-11-21T06:00:12.085000+00:00",
      "url": "https://github.com/advisories/GHSA-gmh6-mmrh-jf9j"
    }
  }
}

published 2026-11-21 06:55Z
last change 2026-11-21 09:10Z

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.