dbcve.org
Memory Buffer Bounds ErrorWeakness · CWE-119

CVE-2025-52264

HIGH · 8.0 CVSS v3.1 Published 2025-10-27
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
82/100
Remediation priority · High
Zero-click

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 · unedited
StarCharge Artemis AC Charger 7-22 kW v1.0.4 was discovered to contain a stack overflow via the cgiMain function at download.cgi.

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 confidence

A stack-based buffer overflow vulnerability exists in the download.cgi web interface component of StarCharge Artemis AC Charger v1.0.4. The vulnerability is located in the cgiMain function and allows potential remote code execution or denial of service via specially crafted input to the download CGI script.

MitigationApply vendor-supplied firmware update when available; until then, restrict network access to the charging station's web interface and monitor for exploitation attempts.

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
Adjacent
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify the device model
    Access the charger admin interface or check the device label/documentation to confirm the product is StarCharge Artemis AC Charger
    Affected if Device is NOT a StarCharge Artemis AC Charger (not affected)
  2. Check firmware version
    Navigate to the web interface Settings or System Info page, or use the charger's management API to retrieve the firmware version
    Affected if Version is 1.0.4 (vulnerable) or if version cannot be determined and the device is StarCharge Artemis AC Charger
  3. Verify web interface is accessible
    Attempt to access the device's web interface via HTTP/HTTPS on the expected management port (typically 80 or 443)
    Affected if Web interface is exposed on network (potential attack surface)
  4. Confirm download.cgi exists
    Try accessing /download.cgi or /cgi-bin/download.cgi on the device's web server
    Affected if The download.cgi script is present and responds to requests
  5. Check for indicators of compromise
    Review web server logs for unusual requests to download.cgi, look for unexpected new files or processes on the device, check for unauthorized configuration changes
    Affected if Logs show anomalous requests to download.cgi or unexpected system changes

The environment is affected if the device is a StarCharge Artemis AC Charger running firmware version 1.0.4 with the web interface and download.cgi script accessible.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply vendor-supplied firmware update when available; until then, restrict network access to the charging station's web interface and monitor for exploitation attempts.

Have this fixed Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
36.0 hours of engineering $6,400
Get help mitigating

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-52264 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-52264 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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