dbcve.org
Cross-site Scripting (XSS)Weakness · CWE-79

CVE-2025-67448

HIGH · 7.1 CVSS v3.1 Published 2026-06-04
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
78/100
Remediation priority · High
Remotely reachable No privileges

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
The SMS module in Neterbit NW-431F Router 20241014-IR03 and before is vulnerable to stored XSS. The application does not properly sanitize user input in SMS messages before storing and displaying them. An attacker can send an SMS containing a malicious XSS payload, which will be executed in the context of the victim's browser when the message is viewed.

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

Stored XSS vulnerability in the SMS module of Neterbit NW-431F Router firmware. The application fails to sanitize user-supplied input in SMS messages before storing them in the database and before rendering them in the web interface, allowing injection of malicious JavaScript that executes when victims view the messages.

MitigationImplement input validation and output encoding/escaping on all SMS message content before storage and display. Apply vendor firmware updates when available.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/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
    Access the router web interface or check the device label/metadata to confirm the model is Neterbit NW-431F
    Affected if The device is a Neterbit NW-431F router
  2. Confirm SMS module is accessible
    Log into the router administration panel and navigate to the SMS messaging section to verify the SMS module is present and accessible
    Affected if The SMS module is available and user can access it
  3. Check for existing SMS messages
    View the SMS inbox or message list in the router SMS interface to see if any messages are stored
    Affected if There are SMS messages stored in the device
  4. Verify SMS display renders HTML content
    Examine the SMS viewing interface to determine if the application displays message content without sanitization - this may require inspecting the page source or testing with a benign payload
    Affected if SMS content is rendered without output encoding and user-supplied input can execute as JavaScript in the browser

A user is affected if they are using a Neterbit NW-431F router with the SMS module enabled and can view SMS messages containing unsanitized user-supplied content.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement input validation and output encoding/escaping on all SMS message content before storage and display. Apply vendor firmware updates when available.

Recommended fix Moderate confidence

Firmware version newer than 20241014-IR03 (contact Neterbit for exact version number)

  1. 1. Identify the current firmware version of the Neterbit NW-431F Router by accessing the administration web interface or checking the device label.
  2. 2. Visit the official Neterbit support website (neterbit.com) or contact Neterbit technical support to request the latest firmware version.
  3. 3. Download the firmware update that addresses CVE-2025-67448 - look for version numbers newer than 20241014-IR03.
  4. 4. Access the router's admin panel, navigate to the firmware upgrade section (usually under Administration or System settings).
  5. 5. Upload and apply the new firmware version, ensuring the device remains powered throughout the update process.
  6. 6. After the router reboots, verify the new firmware version is installed.
  7. 7. Test the SMS module to confirm legitimate SMS messages display correctly and that XSS payloads in test messages are no longer executed.
Caveat Firmware updates may reset router configuration to defaults; backup current settings before upgrading

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

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-67448 — 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-2025-67448 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