dbcve.org
Missing AuthenticationWeakness · CWE-306

CVE-2025-34057

HIGH · 8.7 CVSS v4.0 Published 2025-07-02
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
96/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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
An information disclosure vulnerability exists in Ruijie NBR series routers (known to affect NBR2000G, NBR1300G, and NBR1000 models) via the /WEB_VMS/LEVEL15/ endpoint. By crafting a specific POST request with modified Cookie headers and specially formatted parameters, an unauthenticated attacker can retrieve administrative account credentials in plaintext. This flaw allows direct disclosure of sensitive user data due to improper authentication checks and insecure backend logic. Exploitation evidence was observed by the Shadowserver Foundation on 2025-02-05 UTC.

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

Ruijie NBR series routers (NBR2000G, NBR1300G, NBR1000) contain an unauthenticated information disclosure vulnerability in the /WEB_VMS/LEVEL15/ endpoint. By sending crafted POST requests with modified Cookie headers and specially formatted parameters, attackers can retrieve plaintext administrative credentials. The flaw stems from improper authentication checks and insecure backend logic. Active exploitation was observed in the wild on 2025-02-05.

MitigationApply network access controls to restrict or block external access to the /WEB_VMS/LEVEL15/ endpoint; contact Ruijie for firmware updates; if no patch available, consider network segmentation or replacement of affected devices.

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
Authentication
X
User interaction
None
Scope
X

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

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's web interface or CLI and retrieve the model number and firmware version. In the CLI, this is typically shown in the startup banner or via 'show version' or 'show system-info' commands. Alternatively, check the device label or physical documentation.
    Affected if The device is a Ruijie NBR2000G, NBR1300G, or NBR1000 series router.
  2. Check firmware version
    In the router's web interface, navigate to System Status or Maintenance > Version. In CLI, use 'show version' or 'show firmware-version' if available. Compare the displayed version against any Ruijie firmware releases for these models.
    Affected if The firmware version is older than the latest Ruijie release that addresses this vulnerability.
  3. Verify endpoint exposure
    From an external network location (or from a segment that simulates an external attacker), attempt an HTTP POST request to http://<device-ip>/WEB_VMS/LEVEL15/. Use a tool like curl: curl -X POST -d 'test' http://<device-ip>/WEB_VMS/LEVEL15/. If the endpoint responds (even with an error), it is reachable.
    Affected if The /WEB_VMS/LEVEL15/ endpoint is accessible from an untrusted network segment or the internet.
  4. Inspect for credential-related anomalies
    Log into the router's admin interface and review the administrator accounts under User Management or System Administration. Look for unexpected new accounts, accounts with elevated privileges, or password changes you did not initiate.
    Affected if Unexpected administrative accounts exist or recent credential modifications are found without legitimate admin action.
  5. Review access logs for exploitation attempts
    Check the router's logs (System > Logs or CLI 'show logging') for POST requests to /WEB_VMS/LEVEL15/ with abnormal Cookie headers or parameters. Search for entries containing 'LEVEL15', unusual user-agent strings, or repeated authentication failures.
    Affected if Logs show POST requests to /WEB_VMS/LEVEL15/ with modified Cookie headers or requests that appear to target this endpoint from untrusted sources.

A user is affected if they operate a Ruijie NBR2000G, NBR1300G, or NBR1000 router with the vulnerable endpoint exposed to an untrusted network and running firmware without the CVE fix.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply network access controls to restrict or block external access to the /WEB_VMS/LEVEL15/ endpoint; contact Ruijie for firmware updates; if no patch available, consider network segmentation or replacement of affected devices.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,690
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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