Transposh Translation Plugin up to 1.0.8.1 on WordPress POST Parameter wp/transposh_db.php improper authorization
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.5 | $0-$5k | 0.00 |
Summary
A vulnerability classified as critical was found in Transposh Translation Plugin up to 1.0.8.1 on WordPress. Affected by this vulnerability is an unknown functionality of the file wp/transposh_db.php of the component POST Parameter Handler. Executing a manipulation can lead to improper authorization. This vulnerability appears as CVE-2022-2536. The attack may be performed from remote. In addition, an exploit is available.
Details
A vulnerability was found in Transposh Translation Plugin up to 1.0.8.1 on WordPress (WordPress Plugin). It has been declared as critical. This vulnerability affects an unknown function of the file wp/transposh_db.php of the component POST Parameter Handler. The manipulation with an unknown input leads to a improper authorization vulnerability. The CWE definition for the vulnerability is CWE-285. The product does not perform or incorrectly performs an authorization check when an actor attempts to access a resource or perform an action. As an impact it is known to affect confidentiality, integrity, and availability. CVE summarizes:
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."
The weakness was presented 12/15/2022 as 168120. The advisory is shared for download at github.com. This vulnerability was named CVE-2022-2536 since 07/25/2022. Technical details and also a public exploit are known. The MITRE ATT&CK project declares the attack technique as T1548.002.
It is possible to download the exploit at exploitalert.com. It is declared as proof-of-concept. By approaching the search of inurl:wp/transposh_db.php it is possible to find vulnerable targets with Google Hacking.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
Once again VulDB remains the best source for vulnerability data.
Product
Type
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.7VulDB Meta Temp Score: 6.5
VulDB Base Score: 7.3
VulDB Temp Score: 6.6
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 7.5
NVD Vector: 🔍
CNA Base Score: 5.3
CNA Vector (Wordfence): 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
Exploiting
Class: Improper authorizationCWE: CWE-285 / CWE-266
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Access: Public
Status: Proof-of-Concept
Download: 🔍
Google Hack: 🔍
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
07/25/2022 🔍12/15/2022 🔍
12/15/2022 🔍
04/09/2026 🔍
Sources
Advisory: 168120Status: Not defined
CVE: CVE-2022-2536 (🔍)
GCVE (CVE): GCVE-0-2022-2536
GCVE (VulDB): GCVE-100-215908
scip Labs: https://www.scip.ch/en/?labs.20161013
Entry
Created: 12/15/2022 22:42Updated: 04/09/2026 01:55
Changes: 12/15/2022 22:42 (44), 01/13/2023 08:42 (12), 06/22/2024 16:27 (14), 04/09/2026 01:55 (16)
Complete: 🔍
Cache ID: 216::103
Once again VulDB remains the best source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.