# CVE-2022-2536: Transposh WordPress Translation <= 1.0.9.6 - Authorization Bypass

> Unauthenticated attackers can bypass authorization checks to modify translation settings and influence site content in the Transposh WordPress plugin.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 15 Dec 2022
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-ggf6-w57c-2rj4

## What is CVE-2022-2536?

CVE-2022-2536 is a medium-severity missing authorization vulnerability in oferwald Transposh WordPress Translation, published on 15 Dec 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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."

Weakness: CWE-285 (Improper Authorization)

## Which versions are affected by CVE-2022-2536?

It affects 1 product.


Products: Transposh Transposh Wordpress Translation.

## How do I fix CVE-2022-2536?

No fix has been published for CVE-2022-2536 yet. Limit exposure of the affected software until one is available.

## Is CVE-2022-2536 being exploited?

There is no known exploitation of CVE-2022-2536 in the wild and no public exploit code.

## Other vulnerabilities in oferwald Transposh WordPress Translation

- [CVE-2022-25811](https://insights.sbomify.com/CVE-2022-25811/): Transposh WordPress Translation <= 1.0.8 - Admin+ SQL Injection (high 7.2)
- [CVE-2022-25812](https://insights.sbomify.com/CVE-2022-25812/): Transposh WordPress Translation < 1.0.8 - Admin+ RCE (high 7.2)
- [CVE-2022-25810](https://insights.sbomify.com/CVE-2022-25810/): Transposh WordPress Translation <= 1.0.8 - Subscriber+ Unauthorised Calls (medium 6.5)
- [CVE-2021-24910](https://insights.sbomify.com/CVE-2021-24910/): Transposh WordPress Translation < 1.0.8 - Reflected Cross-Site Scripting (medium 6.1)
- [CVE-2021-24911](https://insights.sbomify.com/CVE-2021-24911/): Transposh WordPress Translation < 1.0.8 - Stored Cross-Site Scripting (medium 5.4)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-2536 and fix it if it is affected.

What it is: CVE-2022-2536 is a medium-severity missing authorization vulnerability in oferwald Transposh WordPress Translation, published on 15 Dec 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-2536 in the wild and no public exploit code.

Affected product: oferwald Transposh WordPress Translation. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2022-2536/ (Markdown: https://insights.sbomify.com/CVE-2022-2536/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2022-2536
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-2536
- OSV: https://osv.dev/vulnerability/CVE-2022-2536

---
From sbomify Insights: https://insights.sbomify.com/CVE-2022-2536/
Summaries are generated and may contain mistakes; the official description above is the record.