CVE
NodePress auth bypass via hardcoded admin password
Affects NodePress 8.5.1 and earlier when NP_ADMIN_DEFAULT_PASSWORD is unset. No fixed version is listed.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
- Exploited
- No known exploitation
- Fix
- No fix listed
- Who is exposed
- Default setups
Do first: Check every install: default setups are affected.
- Last modified
- Whether it needs action now or is a reference record, by fixed rules, with why. Last checked is when cve.now last re-read it.What do these mean? →
- Reference
- Last checked
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 36/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Default setups
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
NodePress through 8.5.1, made by surmon-china, has an authentication bypass that lets a remote attacker without logging in gain full administrator control of the site. The flaw comes from a hardcoded default administrator password, "root", which the attacker submits to the admin login page when the NP_ADMIN_DEFAULT_PASSWORD setting is unset.
Original description
NodePress through 8.5.1 contains an authentication bypass vulnerability that allows unauthenticated attackers to gain administrator access by using the hardcoded default password 'root'. Attackers can send base64-encoded 'root' to POST /admin/login when NP_ADMIN_DEFAULT_PASSWORD is unset to obtain admin tokens and fully control the site.
Who should check
Teams running NodePress 8.5.1 or earlier with NP_ADMIN_DEFAULT_PASSWORD unset, such as default fresh installs
“NodePress through 8.5.1 contains an authentication bypass vulnerability”
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure22/25Default setups, reachable over the network without a login
- Reach?/20Unknown. No tracked technology or package matched
- Severity9.3/10CVSS 9.3
- No patch5/5No patch listed yet
What would change the score
- Would score about 76 if added to CISA KEV
- Would score about 71 if CISA's SSVC rates exploitation active
What to do
Check every install: default setups are affected.
Workaround: The checked facts name no workaround. The stated condition is that NP_ADMIN_DEFAULT_PASSWORD is unset, so keeping that setting defined is the only step the facts point to, though they do not confirm that it closes the bug.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-129955 (NodePress through 8.5.1 Authentication Bypass via Default Administrator Password), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-129955 (entry last updated 2026-11-16):
Affected:
- surmon-china NodePress: through 8.5.1
Fixed versions: none listed yet.
Conditions (all must be true for the bug to be hit):
- NodePress 8.5.1 and earlier (source: https://www.vulncheck.com/advisories/nodepress-through-8.5.1-authentication-bypass-via-default-administrator-password)
- NP_ADMIN_DEFAULT_PASSWORD is unset (source: https://www.vulncheck.com/advisories/nodepress-through-8.5.1-authentication-bypass-via-default-administrator-password)
Setup: the bug is reachable in a default setup; no special feature or setting is needed.
Attacker needs: network access, no login, no user action.
CISA KEV: CVE-2026-129955 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-129955 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/surmon-china/nodepress/issues/143
- https://github.com/surmon-china/nodepress/blob/v8.5.1/src/app.config.ts#L62-L64
- https://github.com/surmon-china/nodepress/blob/v8.5.1/src/modules/admin/admin.service.profile.ts#L48-L64
- https://github.com/surmon-china/nodepress/blob/v8.5.1/src/modules/admin/admin.service.auth.ts#L45-L58
- https://www.vulncheck.com/advisories/nodepress-through-8.5.1-authentication-bypass-via-default-administrator-password
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-129955
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-129955"}.Timeline
- CVE published
- First seen by cve.now
- Posted on X by cve.now
Affected versions
- surmon-china NodePress
through 8.5.1
Evidence 7
CVE record · 2
Establishes: The identifier and description.
- Record
- Record
Other links · 5
- Report
- Repository
- Repository
- Repository
- Link
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-129955
Is CVE-2026-129955 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
When NP_ADMIN_DEFAULT_PASSWORD is unset, an unauthenticated attacker can obtain admin tokens and fully control the site.Source: vulncheck.com
Which versions are affected by CVE-2026-129955?
NodePress: through 8.5.1.Source: cve.now feed data
Am I affected, and how do I check?
NodePress through 8.5.1 is affected when the NP_ADMIN_DEFAULT_PASSWORD setting is unset. To check this, confirm the installed NodePress version and whether NP_ADMIN_DEFAULT_PASSWORD is defined in the site's configuration.Source: vulncheck.com
How do I fix CVE-2026-129955?
The checked facts list no fixed version and no vendor patch ids, so no upgrade target can be named from them.Source: vulncheck.com
What if there's no patch?
The checked facts name no workaround. The stated condition is that NP_ADMIN_DEFAULT_PASSWORD is unset, so keeping that setting defined is the only step the facts point to, though they do not confirm that it closes the bug.Source: vulncheck.com