CVE-2024-25994
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 · uneditedAn unauthenticated remote attacker can upload a arbitrary script file due to improper input validation. The upload destination is fixed and is write only.
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 confidenceAn unauthenticated remote attacker can upload arbitrary script files to a fixed, write-only destination due to improper input validation in the application's file upload functionality. This allows potential code execution if the uploaded script is accessible via a web server.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 1.5.1< 1.5.1< 1.5.1< 1.5.1CVSS 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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
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 Charx Sec modelLocate the device model number on the physical device label or in the device's web interface/system information page. Confirm it is one of: 3000, 3050, 3100, or 3150.Affected if The device model is any of the four listed models.
-
Check the installed firmware versionAccess the device's web interface and navigate to System > Firmware, System > Information, or similar section to view the current firmware version. Alternatively, use the device's CLI or management console to query the firmware version.Affected if The firmware version is less than 1.5.1 (for example, 1.4.x, 1.0.x, etc.).
-
Verify if the web interface is enabledCheck the device's network settings or services configuration to confirm the web-based management interface is active and accessible over HTTP/HTTPS.Affected if The web interface is enabled and reachable on the network.
-
Confirm file upload functionality existsLocate the file upload feature in the web interface, typically found under sections like Maintenance, Firmware Update, Configuration, or Diagnostics. Determine if an unauthenticated or authenticated upload endpoint exists.Affected if A file upload endpoint exists and does not require authentication, or is accessible without proper access controls.
-
Check web server document root configurationExamine the device's web server configuration or documentation to determine where uploaded files are stored and whether that directory is served publicly via the web server.Affected if Uploaded files are stored in a web-accessible directory and can be executed or retrieved via HTTP/HTTPS.
The device is affected if it is a Charx Sec 3000/3050/3100/3150 model running firmware version lower than 1.5.1 with the web interface and file upload feature enabled and accessible.
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.
dbcve · scoped1.5.1
Implement strict input validation for file uploads including whitelist-based file type checking, content validation, and blocking executable extensions; ensure uploaded files are stored outside web-accessible directories.
Charx Sec 3000/3050/3100/3150 Firmware 1.5.1
- Obtain the Charx Sec firmware version 1.5.1 or later from the official vendor source (cert.vde.com or Charx support)
- Access the Charx Sec device management interface via its web-based or administrative console
- Navigate to the firmware update or system upgrade section
- Upload and install the firmware version 1.5.1
- After installation, verify the device is running the patched firmware version
- Restart the device if required to complete the update
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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 $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-25994 — 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-2024-25994 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