Geodirectory - Security Vulnerability (CVE-2026-119113)

Q: Am I affected by this vulnerability?

You are affected if your site runs Geodirectory.

Q: How do I fix it?

Update Geodirectory to the latest available version. Where the vendor has not yet published a fix, remove or disable the plugin until they do. Until you can update, Request / payload inspection (WAF) in Hack Halt ProSecure contains this class of attack at the request layer.

Q: What can an attacker actually do?

This is a Cross-Site Scripting (XSS) flaw. An attacker who exploits it can run script in a visitor's browser, stealing sessions or planting an administrator account.

CVE-2026-119113

Vulnerability CVE-2026-119113 PLUGIN geodirectory MEDIUM

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.

CVE-2026-119113

MEDIUM CVSS 6.4 Published 2026-10-30 Updated 2026-10-30

AI Risk High (83/100) Active Exploit: Likely Published Exploit: Public exploit references found Priority: P2 Urgent

Severity Band MEDIUM

CVSS Vector CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N

Affected Components 2

Reference Links 9

AI Risk Engine High (83/100)

Exploitability High

Active Exploitation Likely

Published Exploit Status Public exploit references found

Threat Timeline

2026-10-30 CVE published and first recorded in the threat feed.
2026-10-30 Record updated with latest vulnerability metadata.
2026-11-07 AI technical context refreshed for mitigation and impact guidance.
Now Monitoring for follow-up changes, linked references, and new related CVEs.

AI Context

Machine-generated threat intelligence

AI Updated 4 days ago

AI enriched 4 days ago (2026-11-07 20:28 UTC)

Technical Summary

Potential Impact

Severity is MEDIUM (CVSS 6.4). Depending on deployment context, affected components may be exposed to unauthorized actions or data integrity risk.

Exploitability Assessment

Exploitability is assessed as High based on published exploit references, remote code execution potential.

Primary risk drivers: published exploit references, remote code execution potential

Mitigation Recommendations

Validate affected product versions, prioritize patching, and monitor references for vendor remediation guidance. If immediate patching is not possible, apply compensating controls and limit exposure of vulnerable surfaces.

Detection & Monitoring

Track authentication anomalies, unexpected file writes, and suspicious plugin API activity around affected components.

Business Impact Lens

AI risk score 83/100 (High, High) with priority P2 Urgent. Prioritize remediation where affected components process customer data, admin sessions, or Internet-exposed workflows.

Affected Products

and Classified Listings Directory PLUGIN · and-classified-listings-directory Affected: <= 2.8.199 Fixed version not specified

Geodirectory PLUGIN · geodirectory Affected: <= 2.8.199 Fixed version not specified

References

What to do about this

Patch on your next cycle Worth fixing, but not ahead of other work.

Fix it

Update Geodirectory to the latest available version.

Where the vendor has not published a fix yet, disable the plugin until they do.

Cannot update today? Request / payload inspection (WAF) in Hack Halt ProSecure blocks this class of attack before WordPress processes the request.

Inspect request parameters and bodies for injection, traversal and file-inclusion payloads, and refuse the request rather than logging it.

Compare Hack Halt plans Start free

Not sure if you are affected?

Scan your site to see whether it runs Geodirectory, and at which version.

Free, no installation, no account. It reads what your site already publishes, then tells you which plugins carry known vulnerabilities and what to do about each one.

Scan my site free See what Hack Halt does

Am I affected by this vulnerability?