Security readout for executives and security teams
Plain-English summary
CVE-2022-2462 affects the Transposh WordPress Translation plugin. Unauthenticated visitors could access translation history data that exposed usernames of people who translated site text. The business impact is limited information disclosure, but exposed usernames can support account targeting, phishing, or password-spraying against WordPress accounts.
Executive priority
Treat this as a moderate-priority WordPress hygiene issue. It does not indicate full site takeover by itself, but exposed usernames can lower the cost of follow-on account attacks. Prioritize public WordPress sites and sites with privileged translators.
Technical view
The flaw is insufficient authorization and overbroad response data in the plugin's tp_history AJAX action. Reported affected versions are up to and including 1.0.9.6. CVSS 3.1 is 5.3: network-reachable, low complexity, no privileges, no user interaction, with low confidentiality impact only.
Likely exposure
Exposure is likely limited to WordPress sites with the Transposh WordPress Translation plugin active at version 1.0.9.6 or earlier. Sites without this plugin are not indicated as affected in the bundle.
Exploitation context
The source bundle does not show CISA KEV listing or confirmed active exploitation. Public third-party technical references exist, including Packet Storm and RCESecurity links, so defenders should assume details are available to attackers without treating this as proven in-the-wild exploitation.
Researcher notes
Evidence supports CWE-200 sensitive information disclosure through tp_history. The bundle identifies affected versions through 1.0.9.6 and references public code/disclosure pages, but does not provide KEV status, active exploitation confirmation, or a clearly named fixed version in the provided text.
Mitigation direction
- Inventory WordPress sites for the Transposh WordPress Translation plugin and its installed version.
- Update the plugin according to vendor or WordPress plugin guidance.
- Disable or remove the plugin where it is unused or cannot be safely updated.
- Review exposed translator accounts for stronger passwords and multi-factor authentication.
- Monitor WordPress authentication logs for suspicious activity against disclosed usernames.
Validation and detection
- Confirm whether Transposh WordPress Translation is installed and active on each WordPress site.
- Verify installed versions are newer than 1.0.9.6, or document vendor guidance if unavailable.
- Check access logs for unauthenticated requests to the plugin's AJAX translation history functionality.
- Review whether translator usernames are sensitive in your operating model.
- Confirm compensating controls such as MFA for affected WordPress accounts.
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-200: Information exposure and cloud metadata lookup
Information exposure and SSRF weaknesses can make discovery, cloud metadata, and credential material review relevant. 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-2022-2462 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
- 5.3 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/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:N/UI:N/S:U/C:L/I:N/A:N3.91.4Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
5.3MediumVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
Source materials
- CVE List V5 sourceCVE List V5
- https://www.wordfence.com/threat-intel/vulnerabilities/id/bd1f12ac-86ac-4be9-9575-98381c3b4291?source=cveCVE reference
- https://plugins.trac.wordpress.org/browser/transposh-translation-filter-for-wordpress/trunk/transposh.php?rev=2682425#L1948CVE reference
- https://www.wordfence.com/vulnerability-advisories/#CVE-2022-2462CVE reference
- https://www.rcesecurity.com/2022/07/WordPress-Transposh-Exploiting-a-Blind-SQL-Injection-via-XSS/CVE reference
- https://packetstormsecurity.com/files/167878/wptransposh1081-disclose.txtCVE reference
- https://github.com/oferwald/transposh/blob/master/transposh.php#L1550CVE 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.
Exposure of Sensitive Information to an Unauthorized Actor
Exposure of Sensitive Information to an Unauthorized Actor represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.