CVE-2025-5873
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA vulnerability was detected in eCharge Hardy Barth Salia PLCC up to 2.3.81. Affected by this issue is some unknown functionality of the file /firmware.php of the component Web UI. Performing a manipulation of the argument media results in unrestricted upload. The attack can be initiated remotely. The exploit is now public and may be used. The vendor was contacted early about this disclosure but did not respond in any way.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceUnrestricted file upload vulnerability in the eCharge Hardy Barth Salia PLCC web interface (firmware.php). Remote attackers can upload arbitrary files via manipulation of the 'media' argument, potentially achieving remote code execution.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify the eCharge Hardy Barth Salia PLCC deviceAccess the device's web interface or check device documentation/metadata to confirm the exact model and firmware version. Compare the installed version against any known version ranges provided by the vendor.Affected if The device is an eCharge Hardy Barth Salia PLCC charging station with an accessible web interface.
-
Verify the firmware.php endpoint is presentAttempt to access the /firmware.php page on the device's web server by navigating to the URL (for example, http://[device-ip]/firmware.php or similar path depending on the web root).Affected if The firmware.php file exists and is accessible on the web interface, indicating the vulnerable component is present.
-
Confirm the file upload functionality is enabledLocate the 'media' parameter within the firmware.php page form or HTTP requests. Determine if the parameter accepts file uploads without proper validation by inspecting the form or testing with a benign file.Affected if The 'media' argument in firmware.php accepts file uploads without apparent restrictions on file type, size, or content.
-
Check for unauthorized files on the web serverReview the web server's upload directory (commonly /uploads, /media, or a directory configured in firmware.php) for unexpected files. Use file system access or HTTP requests to enumerate uploaded files.Affected if Arbitrary or unexpected files (such as executable scripts, shells, or non-image files) are present in the upload directory.
A user is affected if they operate an eCharge Hardy Barth Salia PLCC device with an accessible web interface where the firmware.php upload functionality accepts unrestricted files via the 'media' parameter.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataNetwork-segment the charging station's web interface to limit exposure; implement WAF rules to filter malicious upload requests; monitor for unauthorized firmware uploads. Since the vendor is unresponsive, pursue compensating controls until a firmware patch becomes available.
- Consultation8.0 h
- Implementation16.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $10,240.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-5873 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-5873 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data