Skip to content
vulneraibility.com
Screener

CVE-2023-25717

Ruckus Wireless Admin through 10.4 allows Remote Code Execution via an unauthenticated HTTP GET Request, as demonstrated by a /forms/doLogin?login_username=admin&password=password$(curl substring.

CVSS
9.8Criticalscored by CISA
Exploited in the wild
Yes, in CISA KEV since 12 May 2023CISA deadline for US federal agencies: 2 Jun 2023
EPSS
98.1%chance of exploitation in the next 30 daystop 0.1% of scored CVEsFIRST score of 11 Nov 2026
Fix
Patch availablesee the advisories in the references
Published
13 Feb 2023analysed here 12 Nov 2026

Do first. Apply updates per vendor instructions or disconnect product if it is end-of-life. (CISA's required action for this KEV entry)

Summary

Triage

Attack surface
Server-side
Exploitable
At runtime
Attack vector
network
Weakness
Can a WAF block it?
Partly. See why

The summary, impact and action text on this page are written by our AI analysis pipeline, or taken from the NVD description when a CVE was imported from NVD. They are not the vendor's wording: check them against the sources. A longer AI executive summary and technical analysis are generated for signed-in accounts on the Max plan.

Affected products

Products named in our analysis

  • ruckuswireless:ruckus_wireless_admin
  • ruckuswireless:smartzone_ap
  • commscope:ruckus_smartzone_firmware

Fix and mitigation

WAF and other mitigations

Can a WAF block it? Partly. The attack is delivered via an unauthenticated HTTP GET request with parameters containing command injection syntax, which is unusual and can be detected by a WAF rule matching such suspicious input patterns. A WAF rule can match /forms/doLogin GET request with suspicious command injection syntax in parameters. No tracked WAF vendor has published a rule for this CVE yet, so you would write it yourself.

What a custom rule would match: /forms/doLogin GET request with suspicious command injection syntax in parameters

Also consider: patch · custom WAF rule · remove eval sinks · RASP

Based on an AI reading of the CVE description, and no vendor rule found yet. We check Cloudflare, AWS, Google Cloud Armor and Azure; for Akamai, Imperva, Fastly, F5, ask your vendor.

Remediation steps (AI-written)

Step-by-step remediation is generated for accounts on the Max plan, for CVEs that match a technology in their stack. Add this technology to your stack to see the fix checklist.

Exploitation evidence

CISA KEV catalog
Listed since 12 May 2023.
CISA due date
2 Jun 2023, the remediation deadline for US federal agencies
CISA required action
Apply updates per vendor instructions or disconnect product if it is end-of-life.
Public exploit code
Detection templates only, no public exploit found: 1 Nuclei template
CISA SSVC
exploitation active, automatable yes, technical impact totalAssessed by CISA 29 Jan 2025 (SSVC 2.0.3). Exploitation is none, poc (public proof of concept) or active.

Nuclei

Listed so you can judge urgency, not as a recommendation to run anything. GitHub “proofs of concept” are unvetted: some are fake or carry malware. Exploit-DB marks the entries its staff verified.

Timeline

  1. 13 Feb 2023Published
  2. 12 May 2023Added to CISA KEV (exploited in the wild)87 days (about 3 months) later
  3. 2 Jun 2023CISA remediation due date (US federal agencies)21 days later
  4. 29 Jan 2025CISA SSVC assessment: exploitation active608 days (about 2 years) later
  5. 21 Oct 2025CVE record last updated265 days (about 9 months) later
  6. 12 Nov 2026Analysed by vulneraibility.com387 days (about 1 year) later

CVSS vector

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

MetricValueWhat it means
Attack vectorNetworkReachable over the internet or any routable network.
Attack complexityLowRepeatable attack, no special conditions.
Privileges requiredNoneThe attacker needs no prior access.
User interactionNoneNo victim action needed.
ScopeUnchangedImpact stays within the vulnerable component.
ConfidentialityHighTotal data disclosure possible.
IntegrityHighComplete modification possible.
AvailabilityHighFull outage possible.

Common questions

Is CVE-2023-25717 being exploited?

Yes. CVE-2023-25717 appears in CISA's Known Exploited Vulnerabilities catalog, which means exploitation in the wild has been confirmed and reported. Treat it as active rather than theoretical, and patch it ahead of higher-scoring vulnerabilities that carry no exploitation evidence.

How severe is CVE-2023-25717?

CVE-2023-25717 is rated Critical with a CVSS score of 9.8. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2023-25717?

Yes. A fix has been recorded for CVE-2023-25717. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2023-25717 affect?

CVE-2023-25717 affects ruckuswireless:ruckus_wireless_admin, ruckuswireless:smartzone_ap, commscope:ruckus_smartzone_firmware. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

References

NVDCVE.orgCVE DetailsSource

3 references in the CVE record, grouped by the tags the record gives them.

Other links (3)

Where the data on this page comes from

Summary, impact and triage tags: written by our AI analysis pipeline from the sources above. Check them against the sources.

Similar CVEs

Get CVEs like this by email. Join the free digest: the CVEs we flag as major, all CVSS 8.0 or higher, in up to three emails a day (sent at 05:00, 11:00 and 15:00 UTC). Matching alerts to the products you run needs an account, and accounts are invite-only during the beta.

© 2026 vulneraibility.com