CVE-2025-56009
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 · uneditedCross site request forgery (CSRF) vulnerability in KeeneticOS before 4.3 at "/rci" 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 confidenceCSRF vulnerability in KeeneticOS web interface at the /rci API endpoint allows remote attackers to inject new administrative users by tricking authenticated administrators into visiting malicious pages, enabling full device takeover.
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
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/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 KeeneticOS versionAccess the router's web admin panel and navigate to System > Overview or System > Firmware to view the current OS version. Alternatively, use the command line interface (CLI) and run 'show version' or 'system show version' to display the firmware version.Affected if The displayed version is lower than 4.3 (for example, 4.2.x, 4.1.x, or earlier)
-
Confirm web interface is accessibleVerify that the KeeneticOS web interface (HTTP/HTTPS on ports 80 or 443) is enabled and reachable on the device. This can be confirmed by attempting to access the router's IP address in a web browser or checking the web server status via CLI with 'show interface' or 'show http' commands.Affected if The web interface is enabled and accessible on the network (this is required for the /rci endpoint to be exploitable)
-
Review administrative user accountsLog into the router admin panel and navigate to Users and Passwords or Access Control to list all configured administrator accounts. Alternatively, access the CLI and use 'show administrators' or check the configuration via 'show running-config' to enumerate all user accounts with administrative privileges.Affected if There are unexpected or unauthorized administrative user accounts present that were not created by the legitimate administrator
The environment is affected if KeeneticOS version is below 4.3, the web interface is enabled, and either the version check confirms < 4.3 or suspicious administrative accounts are detected as a potential post-exploitation indicator.
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 to version 4.3 or later. Avoid browsing untrusted sites while logged into the router admin panel as a temporary workaround.
KeeneticOS 4.3
- Download the KeeneticOS 4.3 firmware from the official Keenetic download page
- Access the Keenetic router web interface
- Navigate to System settings or Administration section
- Locate the Firmware/Configuration upgrade option
- Upload and apply the KeeneticOS 4.3 firmware file
- Wait for the device to reboot and verify the upgrade was successful
- Confirm the /rci endpoint is now protected against CSRF attacks
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-56009 — 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-56009 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