PatchSiren cyber security CVE debrief
CVE-2025-41771 Phoenix Contact CVE debrief
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. This SQL injection vulnerability could potentially allow an attacker to manipulate notification messages, although the exact impact on notification functionality is not detailed. Organizations should review the official advisory or CVE record for specific guidance on affected versions and mitigation strategies.
- Vendor
- Phoenix Contact
- Product
- AXC F 1152
- CVSS
- MEDIUM 5.3
- CISA KEV
- Not listed in stored evidence
- Original CVE published
- 2026-08-12
- Original CVE updated
- 2026-09-03
- Advisory published
- 2026-08-12
- Advisory updated
- 2026-09-03
Who should care
Organizations using the affected controller's web interface, security teams responsible for monitoring and patching vulnerabilities, and operators of the affected system should be aware of this vulnerability and take necessary actions to mitigate it. They should review the supplied official advisory or CVE record to validate affected scope, severity, and vendor guidance.
Technical summary
The vulnerability allows an authenticated attacker with low privileges to access an endpoint in the controller's web interface that is vulnerable to SQL injection. The impact is limited to the system's notification functionality, which uses a SQLite database for storing notification messages. This functionality is crucial for system administrators to communicate important information. The vulnerability has a CVSS score of 5.3 and a severity of MEDIUM. To mitigate this vulnerability, organizations should verify and limit access to the vulnerable endpoint, implement input validation and sanitization for user input, and monitor notification functionality for potential anomalies.
Defensive priority
Medium priority due to limited impact on notification functionality
Recommended defensive actions
- Verify and limit access to the vulnerable endpoint
- Implement input validation and sanitization for user input
- Monitor notification functionality for potential anomalies
- Review compensating controls for exposed systems while remediation is scheduled and verified
- Check relevant monitoring, detection, and logs for exposed assets that need extra review
- Track exceptions, retest remediated assets, and close the item only after evidence is documented
- Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up
Evidence notes
Evidence from official CVE Program record and NIST NVD detail page. Limited information available on affected products and versions. The vulnerability affects a SQLite database used only for storing notification messages, which limits the impact to the system's notification functionality. Organizations should verify their exposure and review notification functionality for potential anomalies.
Sources and references
Verified primary and authoritative sources
-
CVE-2025-41771 CVE Program record
Publisher, destination, and source semantics verified
URL: https://www.cve.org/CVERecord?id=CVE-2025-41771
CVE Program - Official CVE Program record with source-provided CVE metadata.
-
CVE-2025-41771 NVD vulnerability detail
Publisher, destination, and source semantics verified
URL: https://nvd.nist.gov/vuln/detail/CVE-2025-41771
NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.
Supplemental references
-
Source reference
Unverified legacy reference
URL: https://phoenixcontact.csaf-tp.certvde.com/.well-known/csaf/white/2026/vde-2025-056.json
Methodology and review provenance
AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.