CVE-2025-56007
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 · uneditedCRLF-injection in KeeneticOS before 4.3 at "/auth" API endpoint allows attackers to take over the device via adding additional users with full permissions by managing the victim to open page with exploit.
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 confidenceCRLF injection vulnerability in the /auth API endpoint of KeeneticOS versions before 4.3 allows attackers to inject malicious HTTP headers via CRLF characters in user input, enabling HTTP response splitting attacks that can lead to device takeover through creation of unauthorized users with full administrative permissions.
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< 4.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
- Required
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/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.
-
Check KeeneticOS firmware versionAccess the Keenetic device web interface or CLI and navigate to System > Firmware or use the 'show version' command to retrieve the current OS versionAffected if The displayed firmware version is below 4.3 (e.g., 4.2.x, 4.1.x, etc.)
-
Verify /auth endpoint is network-accessibleAttempt to reach the /auth API endpoint from an external network location using curl or a browser: curl -I http://<device-ip>/authAffected if The endpoint responds with HTTP headers, indicating it is exposed and reachable
-
Inspect for unauthorized administrative accountsLog into the Keenetic web interface and navigate to Users > Administrator accounts, or use CLI 'show users' command to list all configured admin accountsAffected if There are admin accounts present that were not created by the legitimate administrator
-
Review authentication logs for CRLF injection patternsAccess system logs via the web interface (System > Logs) or CLI 'show log' command and search for entries containing unusual header patterns, multiple authentication attempts, or suspicious user creation eventsAffected if Logs contain entries with unexpected line breaks, duplicate headers, or unauthorized user creation events
A device is affected if it runs KeeneticOS version below 4.3 AND has the /auth endpoint accessible, particularly if unauthorized admin accounts exist or suspicious authentication patterns appear in logs.
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 · scoped4.3
Upgrade KeeneticOS firmware to version 4.3 or later to remediate this vulnerability; if immediate patching is not feasible, restrict external access to the /auth endpoint and monitor for suspicious authentication patterns.
KeeneticOS 4.3
- Upgrade KeeneticOS to version 4.3 or later to remediate the CRLF injection vulnerability in the /auth API endpoint
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-56007 — 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-56007 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