MediumCVE-2023-2745

    WordPress Core < 6.2.1 - Directory Traversal (CVE-2023-2745)

    Published Sources: Debian, CVE.org, OSV

    What is affected, what to do

    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.

    An exploit is publicly available. Update WordPress to version 4.1.38, WordPress to version 4.2.35, WordPress to version 4.3.31.

    Affected
    • WordPress lt *..4.1.38
    • WordPress lt 4.2..4.2.35
    • WordPress lt 4.3..4.3.31
    • WordPress lt 4.4..4.4.30
    • WordPress lt 4.5..4.5.29
    • WordPress lt 4.6..4.6.26
    • WordPress lt 4.7..4.7.26
    • WordPress lt 4.8..4.8.22
    • WordPress lt 4.9..4.9.23
    • WordPress lt 5.0..5.0.19
    • WordPress lt 5.1..5.1.16
    • WordPress lt 5.2..5.2.18
    • WordPress lt 5.3..5.3.15
    • WordPress lt 5.4..5.4.13
    • WordPress lt 5.5..5.5.12
    • WordPress lt 5.6..5.6.11
    • WordPress lt 5.7..5.7.9
    • WordPress lt 5.8..5.8.7
    • WordPress lt 5.9..5.9.6
    • WordPress lt 6.0..6.0.4
    • WordPress lt 6.1..6.1.2
    • WordPress lt 6.2..6.2.1
    Fixed in
    • WordPress 4.1.38
    • WordPress 4.2.35
    • WordPress 4.3.31
    • WordPress 4.4.30
    • WordPress 4.5.29
    • WordPress 4.6.26
    • WordPress 4.7.26
    • WordPress 4.8.22
    • WordPress 4.9.23
    • WordPress 5.0.19
    • WordPress 5.1.16
    • WordPress 5.2.18
    • WordPress 5.3.15
    • WordPress 5.4.13
    • WordPress 5.5.12
    • WordPress 5.6.11
    • WordPress 5.7.9
    • WordPress 5.8.7
    • WordPress 5.9.6
    • WordPress 6.0.4
    • WordPress 6.1.2
    • WordPress 6.2.1

    Not sure whether and how you are affected? Ask a question about this vulnerability

    Metrics

    5.4

    Priority

    XIEM Effective CVSS: highest available CVSS rating from NVD and vendor data.

    Source: Vendor (CNA), CVSS v3

    5.4

    CVSS v3

    Severity Medium on the scale from 0 to 10.

    Source: Debian, CVE.org, OSV

    79.4 %

    EPSS score

    High — model estimates ≥ 50% chance of real-world exploitation within 30 days.

    Source: FIRST EPSS, percentile 99.60

    Show all metrics
    Severity
    Medium
    Priority (0–325)

    The priority score is a consolidated metric that condenses several individual signals into a single, action-guiding ranking: technical severity (CVSS), exploitation likelihood (EPSS), known-exploited status (KEV) and the context of the affected asset. The aim is to answer the only truly important question in vulnerability management: what first?

    Read in glossary
    109.07 Methodology
    Exploit maturity

    An exploit is code or a technique that specifically uses a concrete vulnerability to force unintended behaviour — such as executing code or escalating privileges. It is the tool that turns a theoretical flaw into a practical attack.

    Read in glossary
    PoC (publicly reported)
    XIEM Effective CVSS

    XIEM® is the tiered managed-security operating model from NEOSEC and a registered trademark of NEOSEC GmbH. It extends classic SIEM — the central collection, normalisation and correlation of security-relevant events — with endpoint forensics, network visibility and deception technology, and consolidates them into three building tiers: Sentry, Orchestrate and Command.

    Read in glossary
    5.4 Methodology
    CVSS v3

    CVSS is the globally established, open standard for assessing the technical severity of a vulnerability on a scale from 0 to 10. It describes how easily a flaw can be exploited and what damage it can cause — but not how likely its actual exploitation is. CVSS and the complementary EPSS deliberately answer different questions.

    Read in glossary
    5.4
    EPSS score

    The EPSS score is the absolute model output for an individual vulnerability: the estimated probability of real-world exploitation within the next 30 days, expressed as a value between 0 and 1 (i.e. 0 % to 100 %). A score of 0.42 means „the model estimates a 42 % chance of real-world exploitation within 30 days“.

    Read in glossary
    79.4 %
    High — model estimates ≥ 50% chance of real-world exploitation within 30 days.
    EPSS percentile

    The EPSS percentile is the relative position of a vulnerability within all EPSS-scored CVEs, expressed as a value between 0 and 1. A percentile of 0.90 means „this CVE has a higher EPSS score than 90 % of all other scored CVEs“. Unlike the EPSS score, it is not a probability — but a positioning within a ranking.

    Read in glossary
    99.60
    Critical — this CVE ranks in the top fifth of all CVEs scored today (rank ≥ 80%).
    KEV status

    The KEV catalogue is a list maintained by the US authority CISA of vulnerabilities for which active exploitation in the wild has been confirmed. It answers not the question „how severe?“ but „is it already being attacked?“ — thereby sharply prioritising patching.

    Read in glossary
    —
    Published
    CWE

    CWE is a catalogue of typical weakness types in software and hardware — such as flawed input validation, unsafe memory handling or poor authentication. Where a CVE names a concrete vulnerability in a concrete product, a CWE describes the underlying class of defect.

    Read in glossary
    CWE-22

    Detection rules

    No NEOSEC detection rule is available for this vulnerability yet.

    Classification under NIS2 and CRA

    Rule-based classification from exploitation status and severity. It does not replace a case-by-case assessment.

    NIS2

    NIS2 is EU Directive (EU) 2022/2555 to raise the level of cybersecurity across the Union. It substantially broadens obligations compared with the first NIS directive: more sectors, mandatory risk management, staged reporting duties and personal accountability of senior management.

    Read in glossary
    Handle the vulnerability in regular vulnerability handling under Art. 21(2)(e) NIS2.
    CRA

    The CRA is EU Regulation (EU) 2024/2847 setting horizontal cybersecurity requirements for „products with digital elements“ — from industrial controllers and software to connected consumer devices. For the first time manufacturers must ensure security across the entire product lifecycle, handle vulnerabilities and provide security updates.

    Read in glossary
    From 11.12.2027, Annex I Part II CRA requires manufacturers of affected products with digital elements to handle vulnerabilities without delay and provide security updates.
    ISO/IEC 27001

    ISO/IEC 27001 is the internationally leading standard for an information security management system (ISMS). It describes a risk-based, process-oriented framework to systematically plan, implement, review and improve information security.

    Read in glossary
    Control A.8.8, management of technical vulnerabilities: assess relevance to your systems, plan remediation and keep evidence.

    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.

    Source: Debian Security Advisories, NVD (NIST), OSV (Open Source Vulnerabilities), cvelistv5

    Affected products

    The following versions are affected. Older releases of the same product line are also vulnerable unless stated otherwise.

    Affected products
    Affected versionsFixed in
    WordPress FoundationWordPress
    • 4.5 – < 4.5.29
    • 5.2 – < 5.2.18
    • 5.4 – < 5.4.13
    • 4.8 – < 4.8.22
    • 4.6 – < 4.6.26
    • 5.3 – < 5.3.15
    • 5.1 – < 5.1.16
    • < 4.1.38
    • 6.1 – < 6.1.2
    • 4.4 – < 4.4.30
    • 4.9 – < 4.9.23
    • 6.0 – < 6.0.4
    • 4.7 – < 4.7.26
    • 5.8 – < 5.8.7
    • 5.7 – < 5.7.9
    • 4.2 – < 4.2.35
    • 4.3 – < 4.3.31
    • 5.6 – < 5.6.11
    • 5.0 – < 5.0.19
    • 6.2 – < 6.2.1
    • 5.9 – < 5.9.6
    • 5.5 – < 5.5.12
    • 4.5.29
    • 5.2.18
    • 5.4.13
    • 4.8.22
    • 4.6.26
    • 5.3.15
    • 5.1.16
    • 4.1.38
    • 6.1.2
    • 4.4.30
    • 4.9.23
    • 6.0.4
    • 4.7.26
    • 5.8.7
    • 5.7.9
    • 4.2.35
    • 4.3.31
    • 5.6.11
    • 5.0.19
    • 6.2.1
    • 5.9.6
    • 5.5.12
    wordpresswordpress
    • 5.0 – < 5.0.19
    • 5.2 – < 5.2.18
    • 5.1 – < 5.1.16
    • 4.7 – < 4.7.26
    • 6.2
    • 4.6 – < 4.6.26
    • 4.3 – < 4.3.31
    • 4.4 – < 4.4.30
    • 6.1 – < 6.1.2
    • 5.4 – < 5.4.13
    • 5.9 – < 5.9.6
    • 4.2 – < 4.2.35
    • 5.3 – < 5.3.15
    • 5.8 – < 5.8.7
    • 4.5 – < 4.5.29
    • < 4.1.38
    • 6.0 – < 6.0.4
    • 5.6 – < 5.6.11
    • 5.7 – < 5.7.9
    • 5.5 – < 5.5.12
    • 4.8 – < 4.8.22
    • 4.9 – < 4.9.23
    • 5.0.19
    • 5.2.18
    • 5.1.16
    • 4.7.26
    • —
    • 4.6.26
    • 4.3.31
    • 4.4.30
    • 6.1.2
    • 5.4.13
    • 5.9.6
    • 4.2.35
    • 5.3.15
    • 5.8.7
    • 4.5.29
    • 4.1.38
    • 6.0.4
    • 5.6.11
    • 5.7.9
    • 5.5.12
    • 4.8.22
    • 4.9.23
    Distribution and container packages (21)

    Downstream packages (e.g. Bitnami, Debian, Ubuntu, Red Hat). Versions refer to the distribution, not the vendor.

    Distribution and container packages
    Affected versionsFixed in
    bitnamiwordpress-multisite
    • 6.1.0
    • 5.1.0
    • 5.4.0
    • 4.2.0
    • 6.2.0
    • 4.6.0
    • 4.5.0
    • 5.2.0
    • 5.6.0
    • 5.8.0
    • 6.0.0
    • 4.7.0
    • 5.5.0
    • 4.8.0
    • 5.3.0
    • 4.3.0
    • 4.4.0
    • 4.9.0
    • 5.0.0
    • 5.9.0
    • 5.7.0
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —

    Vendors and products

    Affected operating systems

    Affected operating systems
    Linuxdebianwordpressbookworm
    Linuxdebianwordpressbullseye

    Weakness classes (CWE)

    • CWE-22Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')

      Base

      The product uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the product does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location that is outside of the restricted directory.

      Entry at MITRE CWE-22

    Public exploit references

    Publicly reported proof-of-concepts, exploit modules and detection templates for this vulnerability. NEOSEC links to the original sources only and does not provide any exploit code.

    Public exploit references
    Packet StormWordPress Core 6.2 XSS CSRF Directory Traversal (opens in a new tab)packetstormsecurity.comPoC (publicly reported)reported, not verified—
    Exploit-DBEDB-ID 52274 (opens in a new tab)exploit-db.comPoC (publicly reported)reported, not verified—

    References & sources

    • packetstormsecurity.comfiles/172426/WordPress-Core-6.2-XSS-CSRF-Directory-Traversal.ht…web, x_transferred, Third-party advisory, Vulnerability database
    • core.trac.wordpress.orgchangeset?sfp_email=&sfph_mail=&reponame=&old=55765@/&new=55765…web, Patch
    • lists.debian.orgdebian-lts-announce/2023/06/msg00024.htmlweb, x_transferred
    • wordpress.orgnews/2023/05/wordpress-6-2-1-maintenance-security-releaseweb, Release notes
    • wordfence.comthreat-intel/vulnerabilities/id/edcf46b6-368e-49c0-b2c3-99bf6e2…web, Third-party advisory
    • NVD (NIST)vuln/detail/CVE-2023-2745web
    • exploit-db.comexploits/52274web
    • wordfence.comblog/2023/05/wordpress-core-6-2-1-security-maintenance-release-…web
    Embed badge

    Show the severity and KEV status of this vulnerability on your site – with a link back here. The image is updated hourly.

    Badge preview for CVE-2023-2745
    <a href="https://intel.neosec.eu/en/cve/CVE-2023-2745"><img src="https://intel.neosec.eu/badge/cve/CVE-2023-2745.svg?lang=en" alt="CVE-2023-2745 – NEOSEC Intel" height="20"></a>