CVE-2026-119113 json
GeoDirectory <= 2.8.199 - Authenticated (Subscriber+) Stored Cross-Site Scripting via 'post_content' Parameter
published 2026-10-30 9 d ago modified 2026-10-30 9 d ago also EUVD-2026-114235
- cvss
- 6.4
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.4%
- EPSS 0.4% chance of exploitation in 30 days, percentile 30%
- public exploits
- 0
- none known
Summary
The GeoDirectory – WP Business Directory Plugin and Classified Listings Directory plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the listing description (post_content) in versions up to, and including, 2.8.199 This is due to insufficient input sanitization on save (the bundled geodir_kses_safe_embed_attributes() helper only neutralises data-embed-url, data-src and data-embed, while WordPress core wp_kses_post permits data-* attributes on standard HTML tags) combined with the AyeCode UI library initializing every [data-bs-toggle="popover-html"] element with { html: true, sanitize: false }, which inserts the attacker-controlled data-bs-content value into the popover body as HTML at render time. This makes it possible for authenticated attackers, with Subscriber-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 9 d ago
Exploit prediction
0.36% chance of exploitation in the next 30 days, higher than 30% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 6.4 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N |
Affected products
- paoltaia GeoDirectory – WP Business Directory Plugin and Classified Listings Directory
Classification
- Weakness
-
- CWE-79 Improper Neutralization of Input During Web Page Generation
- Technology feeds
References
- wordfence.com /threat-intel/vulnerabilities/id/df5eb1b8-880d-4d7e-bdca-69bbd9c1ce5e?source=cve
- plugins.trac.wordpress.org /browser/geodirectory/tags/2.8.193/includes/post-functions.php#L2032
- plugins.trac.wordpress.org /browser/geodirectory/tags/2.8.193/includes/class-geodir-post-data.php#L823
- plugins.trac.wordpress.org /browser/geodirectory/tags/2.8.193/includes/formatting-functions.php#L453
- plugins.trac.wordpress.org /browser/geodirectory/tags/2.8.193/vendor/ayecode/wp-ayecode-ui/includes/inc/bs5-js.php#L256
- plugins.trac.wordpress.org /browser/geodirectory/tags/2.8.193/includes/class-geodir-ajax.php#L821
- plugins.trac.wordpress.org /browser/geodirectory/tags/2.8.193/includes/class-geodir-post-data.php#L1666
- github.com /AyeCode/geodirectory/archive/refs/heads/master.zip
- plugins.trac.wordpress.org /changeset/3773530/geodirectory/trunk/vendor/ayecode/wp-ayecode-ui/includes/inc/bs5-js.php
Sources
- CVE List CVE-2026-119113
- NVD CVE-2026-119113
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.