CVE-2025-25271: OCPP Backend Configuration via Insecure Defaults
Noroxi assessment
Priority: Monitor (action score 35/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.34% (FIRST EPSS).
- Someone on the same network segment can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Phoenix Contact CHARX SEC-3000 1.7.3; Phoenix Contact CHARX SEC-3050 1.7.3; Phoenix Contact CHARX SEC-3100 1.7.3.
Low priority for now. Upgrade to Phoenix Contact CHARX SEC-3000 1.7.3; Phoenix Contact CHARX SEC-3050 1.7.3; Phoenix Contact CHARX SEC-3100 1.7.3 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
An unauthenticated adjacent attacker is able to configure a new OCPP backend, due to insecure defaults for the configuration interface.
- Published
- Jul 8, 2025
- Updated
- Jun 17, 2026
- EPSS
- 0.3% · 28th percentile
- CWE
- CWE-1188
Report tools
Action score
35
Monitor
Low priority for now.
- CVSS
- 35 / 40 · 8.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.3%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · CERTVDE
- 8.8
- NVD has not scored this yet; the score shown is the CNA’s.
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| phoenixcontact | charx sec-3000 firmware | cpe:2.3:o:phoenixcontact:charx_sec-3000_firmware |
| phoenixcontact | charx sec-3000 | cpe:2.3:h:phoenixcontact:charx_sec-3000 |
| phoenixcontact | charx sec-3050 firmware | cpe:2.3:o:phoenixcontact:charx_sec-3050_firmware |
| phoenixcontact | charx sec-3050 | cpe:2.3:h:phoenixcontact:charx_sec-3050 |
| phoenixcontact | charx sec-3100 firmware | cpe:2.3:o:phoenixcontact:charx_sec-3100_firmware |
| phoenixcontact | charx sec-3100 | cpe:2.3:h:phoenixcontact:charx_sec-3100 |
| phoenixcontact | charx sec-3150 firmware | cpe:2.3:o:phoenixcontact:charx_sec-3150_firmware |
| phoenixcontact | charx sec-3150 | cpe:2.3:h:phoenixcontact:charx_sec-3150 |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- phoenixcontact charx sec-3000 firmwarebefore 1.7.3
- phoenixcontact charx sec-3050 firmwarebefore 1.7.3
- phoenixcontact charx sec-3100 firmwarebefore 1.7.3
- phoenixcontact charx sec-3150 firmwarebefore 1.7.3
Versions reported by the vendor
Affected version ranges reported by the assigning authority (CERTVDE). Independent of NVD's CPE analysis and usually ahead of it.
Phoenix Contact CHARX SEC-3000
- 0.0.0 and later · before 1.7.3affected · semver
Phoenix Contact CHARX SEC-3050
- 0.0.0 and later · before 1.7.3affected · semver
Phoenix Contact CHARX SEC-3100
- 0.0.0 and later · before 1.7.3affected · semver
Phoenix Contact CHARX SEC-3150
- 0.0.0 and later · before 1.7.3affected · semver
Same product
phoenixcontact: all recordsOther highest-scoring records for the same primary product.
- CVE-2025-25270Remote Code Execution via Unauthenticated Configuration Manipulation39Monitor
- CVE-2024-6788Phoenix Contact: update feature from CHARX controller can be used to reset a low privilege user password39Monitor
- CVE-2024-26001PHOENIX CONTACT: Out of bounds write only memory access39Monitor
Published before and after this one in the same product
- ← EarlierCVE-2025-24006Jul 8, 2025 · Privilege Escalation via Insecure SSH Permissions31Monitor
- ← EarlierCVE-2025-25268Jul 8, 2025 · Unauthenticated Configuration Access via Exposed API Endpoint35Monitor
- ← EarlierCVE-2025-25269Jul 8, 2025 · Local Privilege Escalation via Unauthenticated Command Injection33Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Phoenix Contact CHARX SEC-3000 | 1.7.3 | Vendor (CNA) |
| Phoenix Contact CHARX SEC-3050 | 1.7.3 | Vendor (CNA) |
| Phoenix Contact CHARX SEC-3100 | 1.7.3 | Vendor (CNA) |
| Phoenix Contact CHARX SEC-3150 | 1.7.3 | Vendor (CNA) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
- Sina Kheirkhah (@SinSinology)Summoning Team (@SummoningTeam)finder
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Someone on the same network segment can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Adjacent
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-1188 · Initialization of a Resource with an Insecure DefaultCVSS vector
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Vendor advisories and official records. Exploit/PoC links are deliberately left out.