Security readout for executives and security teams
Plain-English summary
A logged-in WordPress user with Subscriber-level access can save hostile script content in their GeoDirectory display name. If the vulnerable plugin renders that value, the script can run in another user’s browser. This is a moderate business risk, especially for sites allowing public account registration or many low-trust users.
Executive priority
Treat as a scheduled but prompt web-platform fix. It is not KEV-listed and requires authentication, but public-registration sites can turn that into practical exposure. Prioritize internet-facing WordPress properties and sites where administrators regularly view user-generated directory content.
Technical view
CVE-2024-13506 is stored cross-site scripting in GeoDirectory versions up to and including 2.8.97. The issue is insufficient sanitization and output escaping of the display_name profile parameter. The CVSS 3.1 score is 6.4 with low privileges required, changed scope, and limited confidentiality and integrity impact.
Likely exposure
Exposure is limited to WordPress sites running GeoDirectory <= 2.8.97 where an attacker can authenticate as Subscriber or higher. Public registration, customer portals, or broad contributor access increase likelihood. The provided sources do not identify non-WordPress products as affected.
Exploitation context
The CVE record and Wordfence source describe authenticated stored XSS. CISA KEV status is false in the supplied bundle, and no cited source states active exploitation. The attack requires a valid low-privilege account but can affect users who later view pages rendering the stored value.
Researcher notes
The evidence supports CWE-79 stored XSS through display_name with Subscriber-level privileges. The supplied references include vulnerable code location and a WordPress plugin changeset, but the bundle does not explicitly name a fixed release. Avoid claiming active exploitation or broader product impact without additional sources.
Mitigation direction
- Update GeoDirectory according to vendor or WordPress plugin guidance; do not remain on <= 2.8.97.
- Review the referenced WordPress changeset for the escaping and sanitization fix context.
- Restrict public registration or untrusted Subscriber access until the plugin is updated.
- Monitor for suspicious profile display names or unexpected script-like content.
- Check vendor guidance if your exact fixed version is unclear.
Validation and detection
- Inventory WordPress sites using GeoDirectory and record the installed plugin version.
- Confirm vulnerable sites are not running GeoDirectory <= 2.8.97.
- Review whether public registration or low-trust Subscriber accounts are enabled.
- Inspect stored user display names for unexpected markup or script-like content.
- Verify pages rendering user display names escape output after remediation.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-79: User-session and phishing behavior lookup
Client-side and session-facing weaknesses should be reviewed alongside initial-access and user-execution behaviors. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2024-13506 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 6.4 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N3.12.7Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
6.4MediumVector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N
Source materials
- CVE List V5 sourceCVE List V5
- https://www.wordfence.com/threat-intel/vulnerabilities/id/d0d9ba14-c0c9-426e-927e-9139a0882f0d?source=cveCVE reference
- https://plugins.trac.wordpress.org/browser/geodirectory/tags/2.8.97/includes/admin/class-geodir-admin-post-view.php#L317CVE reference
- https://plugins.trac.wordpress.org/changeset/3225839CVE reference
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.