CVE-2025-29512
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 · uneditedCross-Site Scripting (XSS) vulnerability in NodeBB v4.0.4 and before allows remote attackers to store arbitrary code and potentially render the blacklist IP functionality unusable until content is removed via the database.
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 · moderate confidenceA stored Cross-Site Scripting (XSS) vulnerability exists in NodeBB v4.0.4 and prior versions within the IP blacklist functionality. Attackers can inject arbitrary JavaScript code through the blacklist feature, which persists in the database and executes when administrators view the blacklist, potentially compromising admin sessions or rendering the IP blacklist feature unusable until malicious content is manually removed from the database.
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<= 4.0.4CVSS 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.
-
Identify NodeBB versionCheck the installed NodeBB version by examining package.json in the NodeBB installation directory, or run `nodebb version` from the application root, or check the version displayed in the admin control panel under the About sectionAffected if The installed version is 4.0.4 or any prior version (e.g., 4.0.3, 4.0.2, 4.0.1, 4.0.0, or earlier)
-
Access IP blacklist settingsLog into the NodeBB admin control panel and navigate to Settings > IP Blacklist, or directly access the blacklist management interface where administrators configure blocked IP addressesAffected if The IP blacklist feature is accessible and can be viewed or edited by administrators
-
Examine blacklist entries for XSS payloadsInspect the IP blacklist entries in the admin interface for any suspicious content containing script tags, javascript: URLs, event handlers (onclick, onload, etc.), or encoded characters that may indicate injected XSS payloads; alternatively, query the database table storing blacklist entries (commonly found in the database configuration data)Affected if The blacklist contains entries with JavaScript code, script tags, or HTML that could execute in an administrator's browser when viewing the blacklist page
-
Verify admin session integrityAfter accessing the IP blacklist page as an administrator, check if any unexpected script execution occurs, browser alerts fire unexpectedly, or the admin session behaves abnormally; also review any recently added blacklist entries that were not created by authorized administratorsAffected if Unexplained script execution occurs when viewing the blacklist, or unauthorized entries exist in the blacklist that were not added by known administrators
You are affected if running NodeBB version 4.0.4 or earlier AND the IP blacklist contains malicious script entries that execute when administrators access the blacklist management interface.
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.
dbcve · scopedUpgrade to NodeBB version newer than v4.0.4. Additionally, audit and clean any malicious entries already present in the database related to the IP blacklist feature to restore functionality.
NodeBB v4.0.5 or later (latest stable release)
- 1. Back up your NodeBB database and file system before performing any upgrade
- 2. Upgrade NodeBB to the latest stable version beyond v4.0.4 (check the official NodeBB GitHub or releases page for the current stable version)
- 3. After upgrade, verify the blacklist IP functionality works correctly
- 4. If you were previously affected by this XSS, manually review and clean the database to remove any maliciously injected content in the IP blacklist
- 5. Test that the blacklist IP feature renders correctly without executing any stored XSS payloads
Generated from the published advisory — verify against the referenced sources before acting.
- 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-2025-29512 — 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-2025-29512 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