Security readout for executives and security teams
Plain-English summary
A vulnerable Transposh WordPress Translation plugin can let an attacker trick a logged-in authorized user into saving malicious translation content. If that user is an administrator, the stored script can run in the admin’s browser, creating site-takeover risk depending on privileges and session protections.
Executive priority
Treat this as a targeted WordPress plugin risk, not a broad internet-wide emergency. Prioritize affected public sites and administrator-heavy environments because successful stored XSS can undermine site integrity and admin trust.
Technical view
The tp_translation AJAX action lacks CSRF protection, allowing forced translation changes by an authorized user. The tk0 parameter is not sanitized, enabling stored cross-site scripting that executes in the context of a logged-in admin. Sources describe Transposh WordPress Translation versions before 1.0.8.
Likely exposure
Exposure is limited to WordPress sites using Transposh WordPress Translation before 1.0.8. Risk is higher where administrators are active, plugin access is broadly available, or admin sessions lack strong CSRF-aware browser protections.
Exploitation context
The source bundle does not show CISA KEV listing or cited active exploitation. Exploitation requires inducing an authorized logged-in user to submit a crafted request, then waiting for the stored script to execute in an admin context.
Researcher notes
Evidence is sparse: no CVSS vector is provided in the bundle, and exploitation is not reported through KEV. The core chain is CSRF on tp_translation plus missing tk0 sanitization, producing stored XSS in a logged-in admin context.
Mitigation direction
- Inventory WordPress sites for Transposh WordPress Translation installations.
- Confirm installed plugin versions are not below 1.0.8.
- Check vendor or WPScan guidance for fixed release details.
- Temporarily disable the plugin if upgrade guidance is unavailable.
- Restrict administrator browsing and review suspicious translation changes.
Validation and detection
- Check WordPress plugin inventory for Transposh WordPress Translation.
- Verify plugin version against the source-stated before-1.0.8 affected range.
- Review translation entries for unexpected script-like content.
- Inspect admin activity logs around translation updates.
- Confirm no vulnerable plugin remains enabled in production.
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-352: 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 lookupCWE-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-2021-24912 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
- Unknown
- CVSS
- Not scored
- Known Exploited
- No
- Published
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 and timeline data
No CVSS vectors or timeline events were available in the normalized CVE source material.
Source materials
- CVE List V5 sourceCVE List V5
- https://wpscan.com/vulnerability/349483e2-3ab5-4573-bc03-b1ebab40584dCVE reference · x_refsource_MISC
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.
Cross-Site Request Forgery (CSRF)
Cross-Site Request Forgery (CSRF) represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
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.