CVE-2025-1612
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 · uneditedA vulnerability was found in Edimax BR-6288ACL 1.30. It has been declared as problematic. This vulnerability affects unknown code of the file wireless5g_basic.asp. The manipulation of the argument SSID leads to cross site scripting. The attack can be initiated remotely. The vendor was contacted early about this disclosure but did not respond in any way.
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 confidenceA stored cross-site scripting (XSS) vulnerability exists in the Edimax BR-6288ACL wireless router firmware version 1.30. The SSID parameter on the wireless5g_basic.asp configuration page does not properly sanitize user input, allowing an attacker to inject malicious JavaScript code that executes in the context of other users viewing the wireless settings page.
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= 1.30CVSS 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
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/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.
-
Verify firmware version is 1.30Log into the router admin interface and navigate to Status or System Information page to find the firmware version. Alternatively, check the version displayed in the main dashboard or footer of any admin page.Affected if Firmware version is exactly 1.30
-
Confirm wireless5g_basic.asp page existsAccess the router web interface and navigate directly to the wireless5g_basic.asp page, or find the 5GHz wireless settings section in the Wireless or WLAN configuration menu.Affected if The wireless5g_basic.asp configuration page is accessible and present in the firmware
-
Inspect SSID parameter for unsanitized outputView the source HTML of the wireless5g_basic.asp page (right-click > View Page Source) and search for the SSID field value. Check if the SSID is rendered as raw text without HTML entity encoding (look for < instead of <, > instead of >, quote characters without escaping).Affected if The SSID value in the page source contains unescaped HTML special characters like <, >, or unquoted attribute values
-
Check if XSS payload executes in browserIn the wireless SSID field, enter a test string containing a script tag such as <script>alert(1)</script> or an event handler like <img src=x onerror=alert(1)>. Save the settings, reload the page, and observe if the JavaScript executes.Affected if The injected script or event handler executes and triggers a JavaScript alert when viewing the wireless settings page
If the firmware version is 1.30 and the wireless5g_basic.asp page renders SSID values without proper HTML encoding, the router is vulnerable to stored XSS.
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 dataImplement proper input validation and output encoding for the SSID parameter on the wireless5g_basic.asp page. The fix should sanitize special characters and HTML entities before rendering the SSID value in the web interface.
- 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-1612 — 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-1612 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