CVE-2026-29520
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 reflected cross-site scripting vulnerability in the Network Diagnosis ping function that allows attackers to execute arbitrary JavaScript. Attackers can craft malicious links with injected script payloads in the ping_ipaddr parameter to compromise authenticated administrator sessions when the links are visited.
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 confidenceReflected XSS vulnerability in Hereta ETH-IMC408M firmware (v1.0.15 and prior) allows injection of arbitrary JavaScript through the ping_ipaddr parameter in the Network Diagnosis ping function. Attackers can craft malicious links that execute in authenticated administrator sessions when visited.
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
- 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.
-
Confirm device modelAccess the device web interface or CLI and identify the exact model name (Hereta ETH-IMC408M or variant)Affected if Device is not a Hereta ETH-IMC408M model
-
Check firmware versionIn the device web interface, navigate to System Information or Status page to view the firmware version; alternatively, use CLI command such as 'system info' or 'version'Affected if Firmware version is 1.0.15 or lower
-
Verify Network Diagnosis ping function accessibilityLocate the Network Diagnosis or Diagnostics section in the device web interface and confirm the ping function is present and accessible to administratorsAffected if Ping function exists and is accessible to authenticated users
-
Inspect ping_ipaddr parameter handlingAccess the ping function, enter a test value in the ping_ipaddr field (such as a benign test string), and submit the request to observe how the input is reflected in the response without sanitizationAffected if Input is reflected in the response without encoding or validation (visible in page source)
-
Confirm administrator authentication requirementVerify that the ping function requires an authenticated administrator session by attempting access without credentials or reviewing authentication settingsAffected if Ping function is accessible to authenticated administrators (the attack requires this condition)
Device is affected if it is a Hereta ETH-IMC408M with firmware version 1.0.15 or prior, the Network Diagnosis ping function is accessible to authenticated administrators, and the ping_ipaddr parameter reflects user input without sanitization in the response.
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.
From vendor dataUpgrade firmware to a version beyond 1.0.15 that addresses this vulnerability, or implement proper input validation and output encoding on the ping_ipaddr parameter to neutralize script injection.
- 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-29520 — 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-29520 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