CVE-2026-29513
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 · uneditedHereta ETH-IMC408M firmware version 1.0.15 and prior contain a stored cross-site scripting vulnerability that allows authenticated attackers to inject arbitrary JavaScript by manipulating the Device Location field. Attackers can inject malicious scripts through the System Status interface that execute in browsers of users viewing the status page without input sanitation.
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 confidenceThis is a stored (persistent) cross-site scripting vulnerability in Hereta ETH-IMC408M device management firmware. An authenticated attacker can inject malicious JavaScript code into the Device Location field within the System Status interface. Because the input is not sanitized before storage, the payload executes in the browsers of any user subsequently viewing the status 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.0.15CVSS 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.
-
Confirm the device modelAccess the device management interface and identify the exact model name displayed in the system information or device status page. Look for 'Hereta ETH-IMC408M' or similar branding.Affected if The device is not a Hereta ETH-IMC408M model.
-
Check the firmware versionNavigate to the System Status or Device Information page within the management interface. Locate the firmware version field and compare it to the affected range: version 1.0.15 or lower.Affected if The installed firmware version is 1.0.15 or lower.
-
Verify authenticated access to System StatusLog into the device management interface with valid credentials. Navigate to the System Status interface where device information is displayed.Affected if You cannot authenticate to access the management interface.
-
Locate the Device Location fieldWithin the System Status interface, identify the Device Location input field. This field typically allows configuration of a location string for the device.Affected if The Device Location field does not exist or is not editable in your System Status interface.
-
Test for XSS in Device Location fieldUsing the authenticated session, input a test XSS payload such as '<script>alert(1)</script>' into the Device Location field and save. Then reload the System Status page and check if the payload executes or is rendered unsanitized.Affected if The Device Location field reflects injected HTML/JavaScript without encoding or sanitization when displayed on the status page.
You are affected if you are running Hereta ETH-IMC408M firmware version 1.0.15 or lower and the Device Location field in your System Status interface allows unsanitized input to be stored and displayed to other users.
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 · scopedImplement proper input validation and output encoding for the Device Location field and all user-supplied data displayed in the System Status interface. The vendor should release a firmware update that applies context-aware escaping when rendering stored values.
Latest Hereta ETH-IMC408M firmware version after 1.0.15 (contact vendor for specific version number)
- Identify the current firmware version on the ETH-IMC408M device through the admin interface or system settings
- Contact Hereta technical support or visit the official vendor website to obtain the latest firmware version
- Verify that the new firmware version is newer than 1.0.15 and includes a fix for CVE-2026-29513
- Download the firmware update from the official vendor source only
- Review any accompanying release notes or changelog for security fixes
- Follow the vendor's documented firmware update procedure, typically involving uploading the firmware file through the device's web interface or management console
- After updating, verify the Device Location field now properly sanitizes input
- Confirm the new firmware version is applied successfully
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-2026-29513 — 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-2026-29513 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