The GeoDirectory – WP Business Directory Plugin and Classified Listings Directory plugin for WordPress is vulnerable to arbitrary file deletion due to insufficient file path validation in the delete_revision function in all versions up to, and including, 2.8.169. This makes it possible for authenticated attackers, with subscriber-level access and above, to delete arbitrary files on the server, which can easily lead to remote code execution when the right file is deleted (such as wp-config.php). By placing post_type=attachment exclusively in the query string to bypass the consistency check, an attacker can convert an auto-draft GeoDirectory listing into a WordPress attachment with attacker-controlled file paths injected into attachment metadata, which the delete_revision handler then dereferences and unlinks without any post-type or path validation.
CVE-2026-19091
Score 8.1 from GitHub Security Advisory (severity: HIGH) published 2026-08-11. a secondary CVSS source baseline 8.1; sources differ by 0.0.
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 8.1
- EG Score
- 8.1(high)
- EG Risk
- 37(Track)EG Risk 37/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity81% × 45%Exploitation1% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 1%
- EPSS %ILE
- 55%
- KEV
- Not listed
Published
August 11, 2026
Last Modified
August 13, 2026
Advisory Details (5)
Auto-updated Aug 11, 2026Added extra sanitization in AJAX post save - SECURITY
Patch available: AyeCode/geodirectory 2.8.170 (PR #3070 merged 2026-08-06)
https://github.com/AyeCode/geodirectory/pull/3070/changes/29e519019f76a11c74a6b948da655148335f0d18geodirectory/includes/class-geodir-post-data.php at c3969ed65f5c6135d828c47b9f9c162784d1c531 · AyeCode/geodirectory · GitHub
https://github.com/AyeCode/geodirectory/blob/c3969ed65f5c6135d828c47b9f9c162784d1c531/includes/class-geodir-post-data.php#L1658-L1737geodirectory/includes/class-geodir-post-data.php at c3969ed65f5c6135d828c47b9f9c162784d1c531 · AyeCode/geodirectory · GitHub
https://github.com/AyeCode/geodirectory/blob/c3969ed65f5c6135d828c47b9f9c162784d1c531/includes/class-geodir-post-data.php#L1502-L1550geodirectory/includes/class-geodir-post-data.php at c3969ed65f5c6135d828c47b9f9c162784d1c531 · AyeCode/geodirectory · GitHub
https://github.com/AyeCode/geodirectory/blob/c3969ed65f5c6135d828c47b9f9c162784d1c531/includes/class-geodir-post-data.php#L1321-L1326geodirectory/includes/class-geodir-ajax.php at c3969ed65f5c6135d828c47b9f9c162784d1c531 · AyeCode/geodirectory · GitHub
https://github.com/AyeCode/geodirectory/blob/c3969ed65f5c6135d828c47b9f9c162784d1c531/includes/class-geodir-ajax.php#L821-L825Vendor Advisories for CVE-2026-19091(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 27× in last 7d / 41× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-08-20 22:55 UTCEPSS rescore
- 2026-08-20 16:25 UTCGHSA enrichment
- 2026-08-20 03:31 UTCEG score recompute
- 2026-08-20 03:31 UTCGHSA enrichment
- 2026-08-19 17:03 UTCEPSS rescore
- 2026-08-19 14:36 UTCGHSA enrichment
- 2026-08-19 01:40 UTCEG score recompute
- 2026-08-19 01:40 UTCGHSA enrichment
- 2026-08-18 13:48 UTCEPSS rescore
- 2026-08-18 12:45 UTCGHSA enrichment
- 2026-08-17 23:24 UTCEG score recompute
- 2026-08-17 23:24 UTCGHSA enrichment
- 2026-08-17 13:47 UTCEPSS rescore
- 2026-08-17 10:29 UTCGHSA enrichment
- 2026-08-16 21:35 UTCEG score recompute
- 2026-08-16 21:35 UTCGHSA enrichment
- 2026-08-16 14:56 UTCEPSS rescore
- 2026-08-16 08:40 UTCEG score recompute
- 2026-08-16 08:40 UTCGHSA enrichment
- 2026-08-16 02:14 UTCEPSS rescore
- 2026-08-15 19:45 UTCGHSA enrichment
- 2026-08-15 06:50 UTCEG score recompute
- 2026-08-15 06:50 UTCGHSA enrichment
- 2026-08-15 01:30 UTCEPSS rescore
- 2026-08-14 17:21 UTCGHSA enrichment
Show 16 moreShow fewer
- 2026-08-14 04:22 UTCEG score recompute
- 2026-08-14 04:22 UTCGHSA enrichment
- 2026-08-13 22:00 UTCEPSS rescore
- 2026-08-13 15:27 UTCEG score recompute
- 2026-08-13 15:27 UTCGHSA enrichment
- 2026-08-13 15:15 UTCEG score recompute
- 2026-08-13 15:15 UTCGHSA enrichment
- 2026-08-13 09:58 UTCGHSA enrichment
- 2026-08-12 21:04 UTCEG score recompute
- 2026-08-12 21:04 UTCGHSA enrichment
- 2026-08-12 13:50 UTCEPSS rescore
- 2026-08-12 09:14 UTCEG score recompute
- 2026-08-12 09:14 UTCGHSA enrichment
- 2026-08-11 20:19 UTCEG score recompute
- 2026-08-11 19:51 UTCEG score recompute
- 2026-08-11 19:50 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Frequently asked(5)
What is CVE-2026-19091?
When was CVE-2026-19091 disclosed?
Is CVE-2026-19091 actively exploited?
What is the CVSS score of CVE-2026-19091?
How do I remediate CVE-2026-19091?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-19091
Is Your Infrastructure Affected by CVE-2026-19091?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.