What is CVE-2025-41771?

CVE-2025-41771 is SQL injection. The supplied enrichment data classifies it as Injection mapped to CWE-89 SQL Injection.

Which versions are affected?

Affected product and version evidence is listed in the product table above. Current public advisories should be checked for exact version scope before patch targeting is finalized.

Is there active exploitation?

Active exploitation is not confirmed from current sources for CVE-2025-41771. If exploitation is not confirmed from current sources, teams should document that status and continue monitoring KEV, vendor, and telemetry updates.

No. CVE-2025-41771 is not listed in CISA KEV in the supplied enrichment data. KEV status should be monitored because it can change after initial disclosure or after exploitation becomes publicly confirmed.

Is there a public exploit?

2 public PoC repositories reported; 0 marked weaponized in current dataset. Public exploit or PoC availability should raise triage priority, especially for exposed or business-critical systems.

How can defenders detect it?

Start with web/proxy/WAF logs, application logs, network IDS/IPS, database audit logs where available. Look for vulnerability-class behavior, product errors, suspicious authentication events, exploit probes, and abnormal process activity based only on evidence that applies to the affected product.

How should teams prioritize it?

Prioritize CVE-2025-41771 using CVSS 4.3, EPSS 0%, KEV status, public PoC status, and asset exposure. Internet-facing, privileged, or business-critical deployments should be handled first.

Are workarounds available?

The supplied mitigation guidance says to apply vendor patches and restrict external exposure until fixed. Fixed-version evidence is listed in the mitigation section above.

Which threat actors are linked publicly?

No public threat actor linkage is confirmed from current sources. Do not attribute exploitation to a threat actor unless the source evidence explicitly supports that linkage.

What should be done in the next 24 hours?

Identify exposed assets running affected vendor/product/version combinations. Prioritize based on EPSS, PoC availability, and external exposure. Search available logs for exploit probes, errors, authentication anomalies, or suspicious child processes matching the vulnerability class. Open remediation tickets with affected assets, owners, evidence status, and detection coverage so decisions are traceable.

mediumInjectionpublic exploit

CVE-2025-41771

CVE-2025-41771 — SQL injection

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.

Published Aug 12, 2026Updated Aug 12, 2026Sources: NVD, Phoenix Contact (CNA), GitHub, GitHub Security Advisory, SOCRadar CTI

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the scoring sources call it.

Exploitation

Exploit code

public exploit, none observed

EPSS

ahead of 0% of scored CVEs

Affects

Phoenix Contact

17 products listed

CVSS base

4.3

medium · 2 sources

Remediation

The vendor's own words where we have them.

Upgrade AXC F 1152 to a fixed release. Apply vendor patches per advisory and restrict external exposure of the affected component until patched.

First 24 hours

Ordered from the record's own fields — exposure first, because you cannot patch what you have not found.

Identify exposed assets running affected vendor/product/version combinations.
Prioritize based on EPSS, PoC availability, and external exposure.
Search available logs for exploit probes, errors, authentication anomalies, or suspicious child processes matching the vulnerability class.

Affected scope

Vendor, product and version as the advisories word them.

Vendor	Product	Versions	Status
Phoenix Contact	AXC F 1152	2019.0.4 to < 2026.0.3	Vulnerable
Phoenix Contact	AXC F 1252	2019.0.4 to < 2026.0.3	Vulnerable
Phoenix Contact	AXC F 2000 EA	2019.0.4 to < 2026.0.3	Vulnerable
Phoenix Contact	AXC F 2152	2019.0.4 to < 2026.0.3	Vulnerable
Phoenix Contact	AXC F 3152	2019.0.4 to < 2026.0.3	Vulnerable
Phoenix Contact	BPC 9102S	2019.0.4 to < 2026.0.3	Vulnerable
Phoenix Contact	BPC 9202S	2019.0.4 to < 2026.0.3	Vulnerable
Phoenix Contact	RFC 4072R	2019.0.4 to < 2026.0.3	Vulnerable
Phoenix Contact	RFC 4072S	2019.0.4 to < 2026.0.3	Vulnerable
Phoenix Contact	VL3 UPC 2440 EDGE	2019.0.4 to < 2026.0.3	Vulnerable
Phoenix Contact	VPLCNEXT CONTROL 1000	2019.0.4 to < 2026.0.3	Vulnerable
Phoenix Contact	VPLCNEXT CONTROL 2000	2019.0.4 to < 2026.0.3	Vulnerable

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Availability

None

Confidentiality

None

Integrity

Low

Scope

Unchanged

Attack Complexity

Low

Attack Vector

Network

Privileges Req

Low

User Interaction

None

Every base score collected

Sources score independently and disagree; each row says who scored it and under which version.

Score	Version	Severity	Expl.	Impact	Source
4.3	CVSS 3.1	medium	2.8	1.4	NVD, Phoenix Contact (CNA), GHSA
5.3	CVSS 4.0	medium	—	—	Phoenix Contact (CNA)

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N

What this weakness leads to

MITRE's own consequences and mitigations for the weakness class — the authority's wording, not guidance derived from the CVSS vector.

MITRE

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

Read Application Data
Bypass Protection Mechanism
Modify Application Data

Mitigation: Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid. For example, consider using persistence layers such as Hibernate or Enterprise Java Beans, which can provide significant protection against SQL injection if used properly.

Weakness & attack patterns

CWE-89SQL Injection

Attack patterns reported against this CVE. The ATT&CK techniques below are inferred from its weakness class.

CAPEC-470 · Expanding Control over the Operating System from the DatabaseCAPEC-109 · Object Relational Mapping InjectionCAPEC-110 · SQL Injection through SOAP Parameter TamperingCAPEC-7 · Blind SQL InjectionCAPEC-108 · Command Line Execution through SQL InjectionCAPEC-66 · SQL Injection

Public exploit

Capability, not use: code existing is a different claim from anyone running it.

Repositories

Detection

Read off the CVSS vector and the weakness class. Starting points, not rules we have tested.

Prioritize edge telemetry for network-reachable AXC F 1152, AXC F 1252, AXC F 2000 EA, AXC F 2152, AXC F 3152, BPC 9102S, BPC 9202S, RFC 4072R, RFC 4072S, VL3 UPC 2440 EDGE, VPLCNEXT CONTROL 1000, VPLCNEXT CONTROL 2000, VPLCNEXT CONTROL 3000, VPLCNEXT CONTROL 500, Catan C1, EPC 1502, EPC 1522.
Monitor for scanner or exploit-pattern traffic after 2 public PoC repositories were reported.

web/proxy/WAF logsapplication logsnetwork IDS/IPSdatabase audit logs

Timeline

What happened to this CVE, newest first — with the readings a source repeats on a schedule counted underneath rather than listed.

2026
Added · CVSS 3.1 4.3 (AV:N)
Aug 12, 2026 · NVD
Initial · CVE published
Aug 12, 2026 · NVD
Added · GHSA-vr3r-mcqv-4cmg published (medium)
Aug 12, 2026 · GitHub Security Advisory
CVE published by mitre
Aug 12, 2026 · SOCRadar CTI

Source activity

Readings a source repeats on a schedule, counted rather than listed.

1×2 times mentioned on 1 Telegram channelsAug 12, 2026 · SOCRadar CTI

References

3 on the record

phoenixcontact.csaf-tp.certvde.com/.well-known/csaf/white/2026/vde-2025-056.json
Vendor Advisory
nvd.nist.gov/vuln/detail/CVE-2025-41771
NVD
github.com/advisories/GHSA-vr3r-mcqv-4cmg
Exploit, Third Party Advisory

Elsewhere on this site

Phoenix Contactevery CVE for this vendor
Injectionsame class
CWE-89other pages naming this weakness

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record1

What should defenders know first?

CVE-2025-41771 is SQL injection, a medium vulnerability affecting AXC F 1152, AXC F 1252, AXC F 2000 EA, AXC F 2152, AXC F 3152, BPC 9102S, BPC 9202S, RFC 4072R, RFC 4072S, VL3 UPC 2440 EDGE, VPLCNEXT CONTROL 1000, VPLCNEXT CONTROL 2000, VPLCNEXT CONTROL 3000, VPLCNEXT CONTROL 500, Catan C1, EPC 1502, EPC 1522 from Phoenix Contact. The current evidence does not list it in CISA KEV, and the exploit status is: Active exploitation is not confirmed from current sources for CVE-2025-41771. Public exploit evidence is: 2 public PoC repositories reported; 0 marked weaponized in current dataset. The affected-version evidence is listed in the key facts and affected products tables. Defenders should first verify whether exposed or business-critical assets run those versions, then apply vendor patches or mitigations, restrict reachable attack surface, and preserve logs for detection review. CVSS 4.3 describes technical severity, while EPSS 0% helps estimate near-term exploit likelihood; neither replaces asset context. Unknown fields should remain explicit in tickets, and threat actor, IOC, victimology, or payload claims should not be added unless a cited source supports them. Monitor CISA KEV, vendor advisories, NVD changes, public PoC repositories, and internal telemetry for update triggers.