CVE-2025-36750
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 Plant Name field. A HTML payload will be displayed on the plant management page via a direct post. 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 · high confidenceShineLan-X suffers from a stored (persistent) cross-site scripting vulnerability in the Plant Name input field. The application fails to properly sanitize or encode user-supplied input before rendering it on the plant management page, allowing injected JavaScript or HTML payloads to execute in the browsers of users who view the affected plant records.
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.
-
Check the installed firmware versionAccess the ShineLan-X web interface and locate the firmware version information, typically found in System Settings, About, or Device Information pagesAffected if Firmware version is >= 3.6.0.0 and < 3.6.0.2
-
Navigate to plant management interfaceLog into the ShineLan-X web application and locate the plant management or plant configuration section where plant records are created or editedAffected if The Plant Name input field is present and accepts user-supplied values
-
Verify input rendering for XSS vulnerabilitySubmit a test value containing HTML or JavaScript characters (such as <script>alert(1)</script> or <img src=x onerror=alert(1)>) to the Plant Name field, save the record, and view the plant management page to examine how the input is rendered in the HTML sourceAffected if The submitted HTML or script tags execute or are reflected unescaped in the page source, indicating the application fails to sanitize or encode the input
The environment is affected if the installed firmware version falls within the range >= 3.6.0.0 and < 3.6.0.2 AND the Plant Name field allows stored HTML/script content to execute when viewing plant records.
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 strict input validation and output encoding/escaping on the Plant Name field server-side before storage and client-side during rendering. Consider deploying Content Security Policy (CSP) headers to mitigate XSS execution.
3.6.0.2 or later
- 1. Identify the current firmware version of the Shine Lan X device through the administration interface
- 2. Obtain firmware version 3.6.0.2 or later from the official Shine vendor support channels
- 3. Follow the vendor's documented firmware upgrade procedure to apply the update to the device
- 4. After upgrading, verify the new firmware version is 3.6.0.2 or later
- 5. Confirm the Plant Name field now properly sanitizes or encodes HTML/JavaScript input to prevent XSS
Generated from the published advisory — verify against the referenced sources before acting.
- 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-36750 — 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-36750 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