MediumCVE-2025-41771

    SQL injection (CVE-2025-41771)

    Published Last modified Sources: Phoenix Contact PSIRT, CVE.org

    Share

    What is affected, what to do

    An authenticated attacker with low privileges can access an endpoint in the controller’s web interface that is vulnerable to SQL injection. The vulnerability affects a SQLite database used only for storing notification messages.

    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 2019.0.4..2026.0.3
    • Phoenix Contact AXC F 1252 lt 2019.0.4..2026.0.3
    • Phoenix Contact AXC F 2000 EA lt 2019.0.4..2026.0.3
    • Phoenix Contact AXC F 2152 lt 2019.0.4..2026.0.3
    • Phoenix Contact AXC F 3152 lt 2019.0.4..2026.0.3
    • Phoenix Contact BPC 9102S lt 2019.0.4..2026.0.3
    • Phoenix Contact BPC 9202S lt 2019.0.4..2026.0.3
    • Phoenix Contact RFC 4072R lt 2019.0.4..2026.0.3
    • Phoenix Contact RFC 4072S lt 2019.0.4..2026.0.3
    • Phoenix Contact VL3 UPC 2440 EDGE lt 2019.0.4..2026.0.3
    • Phoenix Contact VPLCNEXT CONTROL 1000 lt 2019.0.4..2026.0.3
    • Phoenix Contact VPLCNEXT CONTROL 2000 lt 2019.0.4..2026.0.3
    • Phoenix Contact VPLCNEXT CONTROL 3000 lt 2019.0.4..2026.0.3
    • Phoenix Contact VPLCNEXT CONTROL 500 lt 2019.0.4..2026.0.3
    • Phoenix Contact Catan C1 lt 2019.0.4..2026.0.3
    • Phoenix Contact EPC 1502 lt 2019.0.4..2026.0.3
    • Phoenix Contact EPC 1522 lt 2019.0.4..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 BPC 9202S 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
    • Phoenix Contact Catan C1 2026.0.3
    • Phoenix Contact EPC 1502 2026.0.3
    • Phoenix Contact EPC 1522 2026.0.3

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

    Metrics

    5.3

    Priority

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

    Source: Vendor (CNA), CVSS v4

    4.3

    CVSS v3

    Severity Medium on the scale from 0 to 10.

    Source: Phoenix Contact PSIRT, CVE.org

    0.3 %

    EPSS score

    Low — model estimates < 1% exploitation likelihood.

    Source: FIRST EPSS, percentile 19.7

    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
    51.92 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
    5.3 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
    4.3
    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
    5.3
    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.3 %
    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
    19.7
    Elevated — this CVE ranks above at least 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: partial
    Source: CISA Vulnrichment, as of 12 August 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-89

    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

    An authenticated attacker with low privileges can access an endpoint in the controller’s web interface that is vulnerable to SQL injection. The vulnerability affects a SQLite database used only for storing notification messages. Therefore, the impact is limited to the system’s notification functionality.

    Source: phoenix_contact_advisory, NVD (NIST), 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
    Phoenix ContactAXC F 1152
    • 2019.0.4 – < 2026.0.3
    • 2026.0.3
    Phoenix ContactAXC F 1252
    • 2019.0.4 – < 2026.0.3
    • 2026.0.3
    Phoenix ContactAXC F 2000 EA
    • 2019.0.4 – < 2026.0.3
    • 2026.0.3
    Phoenix ContactAXC F 2152
    • 2019.0.4 – < 2026.0.3
    • 2026.0.3
    Phoenix ContactAXC F 3152
    • 2019.0.4 – < 2026.0.3
    • 2026.0.3
    Phoenix ContactBPC 9102S
    • 2019.0.4 – < 2026.0.3
    • 2026.0.3
    Phoenix ContactBPC 9202S
    • 2019.0.4 – < 2026.0.3
    • 2026.0.3
    Phoenix ContactCatan C1
    • 2019.0.4 – < 2026.0.3
    • 2026.0.3
    Phoenix ContactEPC 1502
    • 2019.0.4 – < 2026.0.3
    • 2026.0.3
    Phoenix ContactEPC 1522
    • 2019.0.4 – < 2026.0.3
    • 2026.0.3
    Phoenix ContactRFC 4072R
    • 2019.0.4 – < 2026.0.3
    • 2026.0.3
    Phoenix ContactRFC 4072S
    • 2019.0.4 – < 2026.0.3
    • 2026.0.3
    Phoenix ContactVL3 UPC 2440 EDGE
    • 2019.0.4 – < 2026.0.3
    • 2026.0.3
    Phoenix ContactVPLCNEXT CONTROL 1000
    • 2019.0.4 – < 2026.0.3
    • 2026.0.3
    Phoenix ContactVPLCNEXT CONTROL 2000
    • 2019.0.4 – < 2026.0.3
    • 2026.0.3
    Phoenix ContactVPLCNEXT CONTROL 3000
    • 2019.0.4 – < 2026.0.3
    • 2026.0.3
    Phoenix ContactVPLCNEXT CONTROL 500
    • 2019.0.4 – < 2026.0.3
    • 2026.0.3

    Vendors and products

    Weakness classes (CWE)

    • CWE-89Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')

      Base

      The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. Without sufficient removal or quoting of SQL syntax in user-controllable inputs, the generated SQL query can cause those inputs to be interpreted as SQL instead of ordinary user data.

      Entry at MITRE CWE-89

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