CVE-2023-49258
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 · uneditedUser browser may be forced to execute JavaScript and pass the authentication cookie to the attacker leveraging the XSS vulnerability located at "/gui/terminal_tool.cgi" in the "data" parameter.
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 Cross-Site Scripting (XSS) vulnerability exists in the /gui/terminal_tool.cgi endpoint where the 'data' parameter is not properly sanitized. An attacker can inject malicious JavaScript that executes in authenticated users' browsers, enabling theft of authentication cookies and session hijacking.
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< 2310271149CVSS 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.
-
Identify the device modelAccess the device web interface or check the device label/CLI to confirm the model is Hongdian H8951Affected if The device is not a Hongdian H8951 model
-
Check the installed firmware versionLog into the device web interface or CLI and locate the firmware version information, typically found in System > Status or System > Firmware. Compare the version number to 2310271149Affected if The firmware version is less than 2310271149 (e.g., 2310271148 or earlier)
-
Verify the vulnerable endpoint existsAttempt to access https://<device_ip>/gui/terminal_tool.cgi in a web browser or via curl. The endpoint should return a response (either login page or access to the tool)Affected if The /gui/terminal_tool.cgi endpoint is accessible and responds to requests
-
Confirm web-based authentication is in useCheck if the device web interface requires login authentication. The XSS vulnerability affects authenticated sessions, so the device must have its web management interface enabled with user authenticationAffected if The device has a web management interface with user authentication enabled (this is required for the attack to target authenticated users)
-
Check session cookie protectionsAfter logging into the web interface, inspect session cookies using browser developer tools or curl -i. Look for the HttpOnly flag on authentication cookiesAffected if Session cookies lack the HttpOnly flag (this indicates the session is vulnerable to JavaScript-based cookie theft)
You are affected if you have a Hongdian H8951 device running firmware version lower than 2310271149 with the web interface and /gui/terminal_tool.cgi endpoint 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 · scoped2310271149
Implement proper input validation and output encoding for the 'data' parameter in terminal_tool.cgi. Additionally, configure Content-Security-Policy headers and set HttpOnly flags on session cookies to prevent JavaScript access.
H8951 4g Esp Firmware version 2310271149 or later
- Identify the current firmware version of the H8951 4g Esp device by accessing the device admin interface or checking system information
- Obtain the fixed firmware version 2310271149 or later from the device vendor's official support or download portal
- Follow the vendor's standard firmware upgrade procedure for the H8951 4g Esp device (typically via web UI or TFTP)
- After completing the firmware upgrade, verify the device is operational
- Test that the /gui/terminal_tool.cgi endpoint properly sanitizes input in the 'data' parameter to confirm the XSS vulnerability is resolved
Generated from the published advisory — verify against the referenced sources before acting.
- 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-2023-49258 — 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-2023-49258 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