Skip to content
Fencer Intel
medium 5.3

CVE-2022-2461 json

Transposh WordPress Translation <= 1.0.9.6 - Unauthorized Settings Change

published 4y ago modified 4mo ago also EUVD-2022-34722

cvss
5.3
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
5.1%
EPSS 5.1% chance of exploitation in 30 days, percentile 92%
public exploits
0
none known, plus a Nuclei check

Summary

The Transposh WordPress Translation plugin for WordPress is vulnerable to unauthorized setting changes by unauthenticated users in versions up to, and including, 1.0.9.6. This is due to insufficient permissions checking on the 'tp_translation' AJAX action and default settings which makes it possible for unauthenticated attackers to influence the data shown on the site.

Patch / fix

Is CVE-2022-2461 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CISA SSVC

Exploitation
Proof of concept is public
Automatable
yes
Technical impact
partial
Assessed
last yr.

Exploit prediction

5.11% chance of exploitation in the next 30 days, higher than 92% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

  • Nuclei template Transposh WordPress Translation <= 1.0.8 - Unauthenticated Settings Change nuclei detection template
  • rcesecurity.com https://www.rcesecurity.com/2022/07/WordPress-Transposh-Exploiting-a-Blind-SQL-Injection-via-XSS/ referenced PoC, tagged "exploit" by a source, unverified
  • packetstormsecurity.com https://packetstormsecurity.com/files/167870/wptransposh107-auth.txt referenced PoC, tagged "exploit" by a source, unverified
  • exploitalert.com https://www.exploitalert.com/view-details.html?id=38891 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
CNA 3.1 5.3 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
NVD 3.1 5.3 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N

Affected products

  • oferwald Transposh WordPress Translation

Classification

Weakness
Technology feeds

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.