CVE-2025-63218
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 · uneditedThe Axel Technology WOLF1MS and WOLF2MS devices (firmware versions 0.8.5 to 1.0.3) are vulnerable to Broken Access Control due to missing authentication on the /cgi-bin/gstFcgi.fcgi endpoint. Unauthenticated remote attackers can list user accounts, create new administrative users, delete users, and modify system settings, leading to full compromise of the device.
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 · high confidenceThe WOLF1MS and WOLF2MS devices contain a broken access control vulnerability where the /cgi-bin/gstFcgi.fcgi endpoint lacks authentication checks. This allows unauthenticated remote attackers to perform administrative operations including listing user accounts, creating new admin users, deleting existing users, and modifying system settings, resulting in full device compromise.
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>= 0.8.5, <= 1.0.3>= 0.8.5, <= 1.0.3CVSS 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
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify device modelAccess the device web interface or check device documentation to confirm whether the device is an Axeltechnology Wolf1ms or Wolf2ms model.Affected if The device is a Wolf1ms or Wolf2ms model.
-
Check firmware versionLog into the device administrative interface and navigate to the firmware or system information page. Note the installed firmware version number.Affected if The installed firmware version is greater than or equal to 0.8.5 and less than or equal to 1.0.3.
-
Verify CGI endpoint is accessibleFrom a browser or using a tool like curl, attempt to access http://<device_ip>/cgi-bin/gstFcgi.fcgi without providing any login credentials.Affected if The endpoint responds with any content or an administrative interface without requiring authentication.
-
Test for unauthenticated administrative operationsSend a request to /cgi-bin/gstFcgi.fcgi with an administrative command parameter (such as listing users or modifying settings) without including any session token or authentication header.Affected if The device processes the command and returns administrative data or confirms the operation without rejecting the request due to missing authentication.
A user is affected if they have an Axeltechnology Wolf1ms or Wolf2ms device running firmware between version 0.8.5 and 1.0.3 where the /cgi-bin/gstFcgi.fcgi endpoint responds without requiring authentication.
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 dataApply the vendor firmware update to address missing authentication. If unavailable, isolate the device behind a firewall or VPN to restrict access to trusted networks only.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-63218 — 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-63218 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