Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in seothemes Display Terms Shortcode display-terms-shortcode allows Stored XSS.This issue affects Display Terms Shortcode: from n/a through <= 1.0.4.
Security readout for executives and security teams
Plain-English summary
CVE-2024-51610 is a stored cross-site scripting flaw in the WordPress Display Terms Shortcode plugin through version 1.0.4. A lower-privileged authenticated user could store content that later runs in another user’s browser when viewed, potentially affecting site administration sessions or visitor trust.
Executive priority
Treat this as a moderate-priority WordPress plugin exposure. Prioritize internet-facing and multi-author sites first, especially where non-admin users can publish or edit content.
Technical view
The issue is CWE-79 improper neutralization during web page generation in seothemes Display Terms Shortcode. CVSS 3.1 is 6.5 with network access, low attack complexity, low privileges required, user interaction required, and changed scope. The source bundle does not identify a fixed version or vendor mitigation.
Likely exposure
Exposure is likely limited to WordPress sites that have the display-terms-shortcode plugin installed at version 1.0.4 or earlier and allow lower-privileged users to create or influence stored term-related output.
Exploitation context
The CVE is not listed as KEV, and the supplied sources do not state active exploitation. Stored XSS still matters because malicious content can persist and execute when a victim views the affected page or admin context.
Researcher notes
The available evidence identifies stored XSS, affected versions through 1.0.4, CVSS 6.5, and CWE-79. It does not provide payload details, affected code paths, proof-of-concept status, exploitation evidence, or a named patched version.
Mitigation direction
Inventory WordPress sites for the display-terms-shortcode plugin and its installed version.
Check vendor or Patchstack guidance for an official fixed release or mitigation.
Disable or remove the plugin if it is not business-critical.
Restrict content and taxonomy management privileges to trusted users.
Review affected sites for suspicious stored content or unexpected redirects.
Validation and detection
Confirm whether display-terms-shortcode is installed on each WordPress property.
Verify whether installed versions are 1.0.4 or earlier.
Review which user roles can create or modify relevant content.
Check recent content and term changes for unexpected script-like entries.
Confirm whether a fixed version is available from authoritative vendor guidance.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
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 · medium confidence lookup
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.
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.
We 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.