HighCVE-2025-41670

    Untrusted Search Path (CVE-2025-41670)

    Published Last modified Sources: CVE.org, EUVD

    Share

    What is affected, what to do

    A local user with low privileges may be able to influence the behavior of a privileged system service by manipulating configuration or application-related files located in user-writable areas of the filesystem. The affected service processes data from locations that are not sufficiently protected against modification by low-privileged users.

    Update Phoenix Contact AXC F 1152 to version 2026.0.3, Phoenix Contact AXC F 1252 to version 2026.0.3, Phoenix Contact AXC F 2000 EA to version 2026.0.3.

    Affected
    • Phoenix Contact AXC F 1152 lt *..2026.0.3
    • Phoenix Contact AXC F 1252 lt *..2026.0.3
    • Phoenix Contact AXC F 2000 EA lt *..2026.0.3
    • Phoenix Contact AXC F 2152 lt *..2026.0.3
    • Phoenix Contact AXC F 3152 lt *..2026.0.3
    • Phoenix Contact BPC 9102S lt *..2026.0.3
    • Phoenix Contact EPC 1522 lt *..2026.0.3
    • Phoenix Contact RFC 4072R lt *..2026.0.3
    • Phoenix Contact RFC 4072S lt *..2026.0.3
    • Phoenix Contact VL3 UPC 2440 EDGE lt *..2026.0.3
    • Phoenix Contact VPLCNEXT CONTROL 1000 lt *..2026.0.3
    • Phoenix Contact VPLCNEXT CONTROL 2000 lt *..2026.0.3
    • Phoenix Contact VPLCNEXT CONTROL 3000 lt *..2026.0.3
    • Phoenix Contact VPLCNEXT CONTROL 500 lt *..2026.0.3
    Fixed in
    • Phoenix Contact AXC F 1152 2026.0.3
    • Phoenix Contact AXC F 1252 2026.0.3
    • Phoenix Contact AXC F 2000 EA 2026.0.3
    • Phoenix Contact AXC F 2152 2026.0.3
    • Phoenix Contact AXC F 3152 2026.0.3
    • Phoenix Contact BPC 9102S 2026.0.3
    • Phoenix Contact EPC 1522 2026.0.3
    • Phoenix Contact RFC 4072R 2026.0.3
    • Phoenix Contact RFC 4072S 2026.0.3
    • Phoenix Contact VL3 UPC 2440 EDGE 2026.0.3
    • Phoenix Contact VPLCNEXT CONTROL 1000 2026.0.3
    • Phoenix Contact VPLCNEXT CONTROL 2000 2026.0.3
    • Phoenix Contact VPLCNEXT CONTROL 3000 2026.0.3
    • Phoenix Contact VPLCNEXT CONTROL 500 2026.0.3

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

    Metrics

    8.7

    Priority

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

    Source: NVD, CVSS v4

    7.8

    CVSS v3

    Severity High on the scale from 0 to 10.

    Source: CVE.org, EUVD

    0.2 %

    EPSS score

    Low — model estimates < 1% exploitation likelihood.

    Source: FIRST EPSS, percentile 8.7

    Show all metrics
    Severity
    High
    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
    61.89 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
    no public PoC known
    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
    8.7 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
    7.8
    CVSS v4

    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
    8.7
    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
    0.2 %
    Low — model estimates < 1% exploitation likelihood.
    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
    8.7
    Low — this CVE sits in the lower 10% of all CVEs scored today.
    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
    CISA assessment (SSVC)
    Exploitation: none known · not automatable · Technical impact: total
    Source: CISA Vulnrichment, as of 27 May 2026
    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-427

    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
    High technical severity: assess and remediate the vulnerability in vulnerability handling under Art. 21(2)(e) NIS2 and document the decision.
    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

    A local user with low privileges may be able to influence the behavior of a privileged system service by manipulating configuration or application-related files located in user-writable areas of the filesystem. The affected service processes data from locations that are not sufficiently protected against modification by low-privileged users. As the service runs with elevated privileges, successful exploitation may result in a local privilege escalation.

    Source: NVD (NIST), CVE.org (MITRE), cvelistv5, ENISA EUVD

    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
    Phoenix ContactAXC F 1152
    • < 2026.0.3
    • 2026.0.3
    Phoenix ContactAXC F 1252
    • < 2026.0.3
    • 2026.0.3
    Phoenix ContactAXC F 2000 EA
    • < 2026.0.3
    • 2026.0.3
    Phoenix ContactAXC F 2152
    • < 2026.0.3
    • 2026.0.3
    Phoenix ContactAXC F 3152
    • < 2026.0.3
    • 2026.0.3
    Phoenix ContactBPC 9102S
    • < 2026.0.3
    • 2026.0.3
    Phoenix ContactEPC 1522
    • < 2026.0.3
    • 2026.0.3
    Phoenix ContactRFC 4072R
    • < 2026.0.3
    • 2026.0.3
    Phoenix ContactRFC 4072S
    • < 2026.0.3
    • 2026.0.3
    Phoenix ContactVL3 UPC 2440 EDGE
    • < 2026.0.3
    • 2026.0.3
    Phoenix ContactVPLCNEXT CONTROL 1000
    • < 2026.0.3
    • 2026.0.3
    Phoenix ContactVPLCNEXT CONTROL 2000
    • < 2026.0.3
    • 2026.0.3
    Phoenix ContactVPLCNEXT CONTROL 3000
    • < 2026.0.3
    • 2026.0.3
    Phoenix ContactVPLCNEXT CONTROL 500
    • < 2026.0.3
    • 2026.0.3

    Vendors and products

    Weakness classes (CWE)

    • CWE-427Uncontrolled Search Path Element

      Base

      The product uses a fixed or controlled search path to find resources, but one or more locations in that path can be under the control of unintended actors.

      Entry at MITRE CWE-427

    References & sources

    Changes to this CVE

    Who changed this CVE and when: NVD (analysis, affected products, CVSS), the CVE publisher (CNA) and additional providers such as CISA (ADP).

    One NVD translation into another language is hidden.

    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-2025-41670
    <a href="https://intel.neosec.eu/en/cve/CVE-2025-41670"><img src="https://intel.neosec.eu/badge/cve/CVE-2025-41670.svg?lang=en" alt="CVE-2025-41670 – NEOSEC Intel" height="20"></a>