CVE-2025-36748
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 · uneditedShineLan-X contains a stored cross site scripting (XSS) vulnerability in the local configuration web server. The JavaScript code snippet can be inserted in the communication module’s settings center. This may allow attackers to force a legitimate user’s browser’s JavaScript engine to run malicious code.
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 · moderate confidenceShineLan-X contains a stored cross-site scripting (XSS) vulnerability in its local configuration web server's communication module settings center. Attackers can inject malicious JavaScript code into this settings area, which then executes in the browsers of legitimate users who access the affected functionality.
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>= 3.6.0.0, < 3.6.0.2CVSS 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
- Low
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/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.
-
Identify the Shine Lan X firmware versionAccess the device's web interface or check the device management console for the installed firmware version. The firmware version is typically displayed in the device status or system information page.Affected if The installed firmware version is 3.6.0.0 or 3.6.0.1 (any version >= 3.6.0.0 and < 3.6.0.2).
-
Confirm the communication module settings center existsNavigate to the local configuration web server interface and locate the communication module settings center. This is typically found under the settings or configuration section of the web interface.Affected if The communication module settings center is accessible and present in the web interface.
-
Verify web interface is reachableAttempt to access the device's web interface via HTTP/HTTPS on the expected management port (commonly port 80 or 443, or a custom port as configured).Affected if The web interface is accessible over the network, making the XSS vector reachable.
You are affected if the installed firmware version is 3.6.0.0 or 3.6.0.1 AND the web-based communication module settings center is accessible.
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 · scoped3.6.0.2
Implement proper input validation and output encoding/sanitization on all user-supplied data in the communication module's settings center. Consider implementing Content Security Policy (CSP) headers as an additional defense-in-depth measure.
Firmware version 3.6.0.2 or later
- Access the Shine Lan X device administration interface
- Navigate to the communication module's settings center
- Identify any stored XSS payloads that may have been injected into configuration fields
- Remove any malicious JavaScript code that was inserted into the settings
- Upgrade the firmware from the current version (3.6.0.0 or 3.6.0.1) to version 3.6.0.2 or later
- After upgrading, verify that the XSS vulnerability is no longer present by attempting to inject a benign test script into the same settings fields
- Confirm the fix by logging out and back in, then checking that the injected script does not execute
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-36748 — 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-36748 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