dbcve.org
Eth Imc408m FirmwareOperating system · Hereta

CVE-2026-29510

MEDIUM · 5.4 CVSS v3.1 Published 2026-03-16
Fix available
A fix is available. Upgrade to after 1.0.15 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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 · unedited
Hereta 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 Name 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 · high confidence

This is a stored cross-site scripting (XSS) vulnerability in the Hereta ETH-IMC408M industrial monitoring camera firmware. An authenticated attacker can inject arbitrary JavaScript code into the Device Name field within the System Status interface. The malicious payload is stored on the device and executes in the browsers of any users who view the status page, because the application fails to sanitize input or encode output.

MitigationImplement input validation and output encoding for the Device Name field in the System Status interface. Apply context-appropriate escaping when rendering user-supplied data in web pages. Deploy a patched firmware version if available, and consider implementing Content Security Policy headers to mitigate XSS execution.

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
Eth Imc408m FirmwareOperating system
Affected:<= 1.0.15

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify the device model
    Locate the physical device or log into the web interface and check the model number displayed in the device information or System Status page. Confirm it is a Hereta ETH-IMC408M industrial monitoring camera.
    Affected if The device model is Hereta ETH-IMC408M and the firmware version is <= 1.0.15
  2. Check the firmware version
    In the web interface, navigate to System Status or a Firmware/About section and locate the firmware version number. Compare this against the affected range of <= 1.0.15.
    Affected if The installed firmware version is 1.0.15 or lower
  3. Verify the web interface is accessible
    Confirm that the web management interface is enabled and accessible on the device. Attempt to reach the HTTP/HTTPS login page.
    Affected if The web interface is enabled and reachable on the network
  4. Examine the Device Name field in System Status
    Log into the web interface and navigate to the System Status page. Locate the Device Name field and inspect its current value. View the page source or use browser developer tools to check if the value is rendered with proper encoding (look for HTML entities like &lt; &gt; &quot; instead of raw < > " characters).
    Affected if The Device Name field contains unsanitized HTML or JavaScript characters that are rendered directly without encoding, or if arbitrary script tags can be injected and execute upon page reload

A user is affected if they have a Hereta ETH-IMC408M camera running firmware version 1.0.15 or lower, with the web interface enabled, and the Device Name field in System Status renders user-supplied input without sanitization or output encoding.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to a release after 1.0.15
Interim mitigation

Implement input validation and output encoding for the Device Name field in the System Status interface. Apply context-appropriate escaping when rendering user-supplied data in web pages. Deploy a patched firmware version if available, and consider implementing Content Security Policy headers to mitigate XSS execution.

Recommended fix Moderate confidence

Latest available ETH-IMC408M firmware version (v1.0.16 or later)

  1. 1. Identify the current firmware version of the Hereta ETH-IMC408M device through the web interface or administrative console.
  2. 2. Access the vendor's official support or download page for the ETH-IMC408M product.
  3. 3. Download the latest available firmware version for the ETH-IMC408M device.
  4. 4. Review the firmware release notes to confirm the version includes a fix for stored XSS in the Device Name field (CVE-2026-29510).
  5. 5. Back up the current device configuration before proceeding with firmware update.
  6. 6. Upload and apply the new firmware through the device's administrative interface, following vendor-provided upgrade instructions.
  7. 7. After reboot, verify the new firmware version is installed and confirm the Device Name field now properly sanitizes input.
Caveat Review vendor release notes for any configuration or compatibility changes before upgrading

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Eth Imc408m Firmware Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-29510 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-29510 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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