Radar sectionsDatabase
Check my site
WordPress plugin

Transposh WordPress Translation <= 1.0.9.6 — Authorization Bypass

CVE-2022-2536Published · Updated

Action summary

Affected: ≤1.0.9.6No patch available

What to do until a fix ships
Severity
Medium5.3
CVSS
5.3
CVSS 3.1 · CNA (Wordfence)
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
What does this vector mean?
AV:N Attack vector
Network
AC:L Attack complexity
Low
PR:N Privileges required
None
UI:N User interaction
None
S:U Scope
Unchanged
C:N Confidentiality
None
I:L Integrity
Low
A:N Availability
None
Weakness
CWE-285 Improper Authorization
Required access
No account needed
Exploit prediction (EPSS)
No score
CISA KEV
Not listed

Am I affected?

Transposh WordPress Translation transposh-translation-filter-for-wordpress

  1. Affected≤ 1.0.9.6
  2. PatchedNo fix yet

No patched version available.

You are affected if you run ≤ 1.0.9.6. No fixed version has been released.

  • Check your version: in wp-admin go to Plugins → Installed Plugins and read the version under Transposh WordPress Translation.
  • No admin access? Run a passive check of your site. It reads public files only.
  • No account is needed to exploit this. Treat any exposed site on an affected version as at risk.

What to do

  1. No known patch available. Please review the vulnerability's details in depth and employ mitigations based on your organization's risk tolerance. It may be best to uninstall the affected software and find a replacement.
  2. Rotate administrator passwords and application secrets if the site ran a vulnerable version while publicly reachable.
  3. Watch Transposh WordPress Translation to get an email when the next vulnerability is published.

Advisory

Source description from Wordfence Intelligence, credited to Julien Ahrens.

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 validation of settings on the 'tp_translation' AJAX action which makes it possible for unauthenticated attackers to bypass any restrictions and influence the data shown on the site. Please note this is a separate issue from CVE-2022-2461. Notes from the researcher: When installed Transposh comes with a set of pre-configured options, one of these is the "Who can translate" setting under the "Settings" tab. However, this option is largely ignored, if Transposh has enabled its "autotranslate" feature (it's enabled by default) and the HTTP POST parameter "sr0" is larger than 0. This is caused by a faulty validation in "wp/transposh_db.php."

Exploits & references

Proof-of-concept & detection

No public proof-of-concept or detection template is known for this vulnerability.

Advisories & patches

More in Transposh WordPress Translation

All 9
More vulnerabilities in Transposh WordPress Translation
SeverityVulnerabilityCVEPublished
Medium6.5 Unauthenticated Stored Cross-Site Scripting via 'tp_translation'
≤1.0.7Update to 1.0.8
CVE-2021-24911
Medium4.3 Cross-Site Request Forgery
≤1.0.9.1Update to 1.0.9.2
CVE-2021-24912
Medium6.3Missing Authorization Checks
≤1.0.9.1Update to 1.0.9.2
CVE-2022-25810
Medium6.1Reflected Cross-Site Scripting via tp_tp
≤1.0.7Update to 1.0.8
CVE-2021-24910
Medium4.9Authenticated (Admin+) SQL Injection via 'tp_editor'
≤1.0.9.1Update to 1.0.9.2
CVE-2022-25811

Timeline

  1. CVE published

    Severity medium, CVSS 5.3

  2. Record last updated

Sources & licenses

Wordfence record
Vulnerability data
Wordfence Intelligence. Copyright 2012-2026 Defiant Inc. Licensed under the CC BY-SA 4.0.
CVE® identifiers
Copyright 1999-2026 The MITRE Corporation. Used under the CVE Program. CVE® is a registered trademark of The MITRE Corporation.
CVSS / CWE
National Vulnerability Database (NVD), shown unmodified. This product uses the NVD API but is not endorsed or certified by the NVD.
VulnCrest content
Summary, remediation guidance and page layout © VulnCrest. Not sourced from NVD.

How we use these sources

Search VulnCrest Radar

Are you sure?