CVE-2025-26063
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 issue in Intelbras RX1500 v2.2.9 and RX3000 v1.0.11 allows unauthenticated attackers to execute arbitrary code via injecting a crafted payload into the ESSID name when creating a network.
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 confidenceCommand injection vulnerability in Intelbras RX1500 v2.2.9 and RX3000 v1.0.11 allows unauthenticated remote attackers to execute arbitrary operating system commands by injecting malicious payloads into the ESSID name parameter when creating a wireless network.
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= 2.2.9= 1.0.11CVSS 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 the device modelAccess the device's web management interface or check the physical label/console output to confirm the model is Intelbras RX1500 or RX3000.Affected if The device is not an Intelbras RX1500 or RX3000, this CVE does not apply.
-
Check the firmware version on RX1500Log into the web interface, navigate to Status or System settings, or use the command line to retrieve the firmware version. For RX1500, look for version 2.2.9.Affected if The firmware version is exactly 2.2.9 on an RX1500 device.
-
Check the firmware version on RX3000Log into the web interface, navigate to Status or System settings, or use the command line to retrieve the firmware version. For RX3000, look for version 1.0.11.Affected if The firmware version is exactly 1.0.11 on an RX3000 device.
-
Verify web interface accessibilityDetermine if the device's administrative web interface (typically on ports 80 or 443) is reachable from untrusted networks such as the internet or guest networks.Affected if The web management interface is exposed to untrusted networks, the command injection can be exploited remotely without authentication.
-
Check for unauthorized network configurationsReview the device's wireless network settings to see if any unexpected or unauthorized SSIDs have been created, which may indicate exploitation of this vulnerability.Affected if Unexpected or suspicious SSIDs exist in the network configuration that were not created by an authorized administrator.
You are affected if you have an Intelbras RX1500 running firmware 2.2.9 or an RX3000 running firmware 1.0.11, and the web management interface is accessible (especially from untrusted networks), because the vulnerability allows unauthenticated command injection via the ESSID parameter when creating a new network.
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 vendor firmware updates when available; until then, restrict access to the device management interface via firewall rules or VLAN isolation to prevent unauthenticated attackers from reaching the vulnerable endpoint.
- Consultation2.0 h
- Implementation4.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 $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-26063 — 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-26063 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