CVE-2023-2745
MediumExploitedPublic exploitWordPress Core is vulnerable to Directory Traversal in versions up to, and including, 6.2, via the ‘wp_lang’ parameter.
Published May 17, 2023 · Updated Sep 8, 2026 · Also known as BIT-wordpress-2023-2745, BIT-wordpress-multisite-2023-2745, DEBIAN-CVE-2023-2745, DLA-3462-1, DSA-5685-1, UBUNTU-CVE-2023-2745, edcf46b6-368e-49c0-b2c3-99bf6e2d358f
Key Facts
Patch immediately- CVE-2023-2745 is a medium-severity vulnerability (CVSS 6.1 v3.1) affecting WordPress, wordpress-multisite (bitnami).
- It is exploited in the wild, listed in Industry KEV feed since May 4, 2026. Public exploit code is available.
- EPSS estimates a 80% probability of exploitation in the next 30 days.
- Fixed versions are available, including WordPress 4.1.38, WordPress 4.2.35, WordPress 4.3.31.
- Brandefense priority: patch immediately, because it is listed as exploited in the wild.
CVSS v3.1
6.1
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
EPSS (30-day exploit likelihood)
80%
Higher than 99.6% of all scored CVEs
Exploited in the wild
Yes
1 catalog listing
Public exploit code
Available
Proof-of-concept or weaponized module
Get the full CVE-2023-2745 brief as a PDF
Every affected product and fixed release, exploitation status and a first 24 hours response checklist, emailed within minutes.
Description
WordPress Core is vulnerable to Directory Traversal in versions up to, and including, 6.2, via the ‘wp_lang’ parameter. This allows unauthenticated attackers to access and load arbitrary translation files. In cases where an attacker is able to upload a crafted translation file onto the site, such as via an upload form, this could be also used to perform a Cross-Site Scripting attack.
Known-Exploited Catalog Listings
| Catalog | Added | Remediation due | Ransomware use |
|---|---|---|---|
| Industry KEV feed | May 4, 2026 | n/a | Not reported |
Required action: Apply remediations or mitigations per vendor instructions or discontinue use of the product if remediation or mitigations are unavailable.
Affected Products
22 affected entries in total| Product | Affected versions | Fixed in |
|---|---|---|
| WordPressWordpress | 6.2, >= 4.2 | 4.1.38 |
| wordpress-multisitebitnami | See advisory | 4.1.38 |
Patched Releases
WordPress
4.1.38, 4.2.35, 4.3.31, 4.4.30, 4.5.29, 4.6.26, 4.7.26, 4.8.22, 4.9.23, 5.0.19, 5.0.19+dfsg1-0+deb10u1, 5.1.16, 5.2.18, 5.3.15, 5.4.13, 5.5.12, 5.6.11, 5.7.11+dfsg1-0+deb11u1, 5.7.9, 5.8.7, 5.9.6, 6.0.4, 6.1.2, 6.1.6+dfsg1-0+deb12u1, 6.2.1, 6.2.1+dfsg1-1
wordpress-multisite
4.1.38, 4.2.35, 4.3.31, 4.4.30, 4.5.29, 4.6.26, 4.7.26, 4.8.22, 4.9.23, 5.0.19, 5.1.16, 5.2.18, 5.3.15, 5.4.13, 5.5.12, 5.6.11, 5.7.9, 5.8.7, 5.9.6, 6.0.4, 6.1.2, 6.2.1
Timeline
Publicly disclosed
May 17, 2023
Added to Industry KEV feed
May 4, 2026
Last updated
Sep 8, 2026
Weakness Type
- CWE-22 Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
References
- advisoryhttp://packetstormsecurity.com/files/172426/WordPress-Core-6.2-XSS-CSRF-Directory-Traversal.html
- advisoryhttps://core.trac.wordpress.org/changeset?old=55765&new=55765
- advisoryhttps://github.com/CVEProject/cvelistV5/tree/main/cves/2023/2xxx/CVE-2023-2745.json
- advisoryhttps://security-tracker.debian.org/tracker/CVE-2023-2745
- advisoryhttps://ubuntu.com/security/CVE-2023-2745
FAQ
Common Questions.
WordPress Core is vulnerable to Directory Traversal in versions up to, and including, 6.2, via the ‘wp_lang’ parameter.
Affected: WordPress versions 6.2, >= 4.2; wordpress-multisite (bitnami). The full list is in the CVE brief.
It is exploited in the wild, listed in Industry KEV feed since May 4, 2026.
No, it is not currently listed in the CISA Known Exploited Vulnerabilities catalog.
Public exploit code is available.
Fixed versions are available, including WordPress 4.1.38, WordPress 4.2.35, WordPress 4.3.31.
Brandefense priority: patch immediately, because it is listed as exploited in the wild.
Is CVE-2023-2745 Running On Your Attack Surface?
Brandefense maps vulnerabilities like this one to your internet-facing assets and tells you exactly where to patch.
Request A Demo