Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessControl valid remote ActivityPub actor
-
DeliveryCraft Create object with attributedTo:1
-
ExploitSend signed activity to federation inbox
-
ExecutionMiddleware verifies signature but not attributedTo
-
PersistPost/DM created as administrator uid
-
ImpactForged content impersonates local admin
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A08:2025 - Software or Data Integrity Failures
ASVS 5.0
V15 - Secure Coding and Architecture Data authenticity verification
|
| Exploitation Conditions | Requires the target NodeBB instance to have the ActivityPub/federation feature explicitly enabled - this is the primary gating precondition and is non-default. The attacker must operate a remote federated actor capable of producing a valid HTTP signature that passes the inbound middleware's actor and object.id origin checks, but needs no local NodeBB account or credentials (PR:N). The concrete forgery is achieved by setting the inbound object's attributedTo to a bare numeric local uid (e.g. 1 for the administrator), which actors.assert filters out without re-deriving, causing the post or DM to be created under that local uid. Limiting factors: instances without federation enabled are not exploitable, and success depends on the target running an affected NodeBB 4.x build with the unpatched mocks.js author-binding logic. |
| Impact | The supplied CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H) scores 8.7 and reflects a network-reachable, low-complexity, unauthenticated attack with high integrity impact and no confidentiality or availability impact - consistent with an impersonation/forgery flaw. Public POC availability from VulnCheck raises practical exploitability, but the absence of CISA KEV listing and the requirement that ActivityPub federation be explicitly enabled temper widespread real-world risk toward targeted rather than mass exploitation. No EPSS score was provided in the input, so probabilistic exploitation likelihood cannot be quantified here. One caveat to verify: the vendor vector uses AT:N, yet the description states federation must be enabled - a genuine precondition - so the effective attack surface is narrower than a default-config network flaw; treat AT/AC as arguably understated. Overall this is a real, high-integrity priority for any NodeBB instance running federation, and low-to-moderate for the broader NodeBB population that has not enabled ActivityPub. |
| Exploit ScenarioDerived | An attacker stands up (or controls) a remote ActivityPub actor that can produce a valid HTTP signature, then sends a Create activity to a federation-enabled NodeBB instance with attributedTo set to the bare numeric value 1. NodeBB accepts the value as the local author uid and creates the post or private message as the administrator, letting the attacker publish forged announcements or send DMs that appear to come from staff. Public POC code demonstrating this is available at the referenced GitHub repository, and the low-complexity network vector makes the attack straightforward to reproduce. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv3 – Jul 01, 2026
Author spoofing in NodeBB's ActivityPub federation allows a remote federated actor to forge posts and private messages attributed to arbitrary local users, including the administrator (uid 1). Because the inbound middleware validates the HTTP-signature actor and the origin of object.id but never binds attributedTo to the authenticated sender, an attacker with a valid remote signature can impersonate any local account. Publicly available exploit code exists (reported by VulnCheck), though there is no public exploit identified in CISA KEV and the flaw only affects instances with federation enabled.
Earlier versions of this analysis (2)
Author spoofing in NodeBB's ActivityPub federation allows a remote attacker to forge posts and direct messages attributed to arbitrary local users, including the administrator (uid 1). Because inbound object handling trusts the attacker-controlled attributedTo field as a local uid rather than binding it to the HTTP-signature-verified remote actor, any federated peer can impersonate local accounts. Publicly available exploit code exists (reported by VulnCheck); there is no public exploit identified as actively exploited, and the flaw only affects instances with the ActivityPub/federation feature enabled.
Author spoofing in NodeBB's ActivityPub federation lets a remote federated actor forge posts and private messages attributed to arbitrary local users, including the administrator, by setting the inbound object's attributedTo to a bare local uid such as 1. The inbound middleware verifies the HTTP-signature actor and the origin of object.id but never binds attributedTo to the authenticated sender, and actors.assert silently drops numeric identifiers instead of re-deriving the uid, so the local uid is trusted as authored. Publicly available exploit code exists (reported by VulnCheck); this is not listed in CISA KEV. Exploitation requires the ActivityPub/federation feature to be enabled.
RemediationAI
Upgrade NodeBB to a release in which inbound ActivityPub processing binds attributedTo to the HTTP-signature-verified remote actor and re-derives (rather than trusts) the local uid; a released patched version could not be independently confirmed from the provided data, so consult the VulnCheck advisory (https://www.vulncheck.com/advisories/nodebb-activitypub-author-spoofing-via-unvalidated-attributedto-mapped-to-local-user) and the NodeBB project for the exact fix version before deploying. As an immediate compensating control where patching is not yet possible, disable the ActivityPub/federation feature in the admin panel - this fully removes the attack surface at the cost of losing all federation and inbound remote interaction. If federation must remain on, restrict or filter inbound federation traffic to trusted instances via an allowlist at the application or reverse-proxy layer and monitor for posts or DMs whose author is a privileged local account (e.g. uid 1) arriving through the federation inbox; note this is detection and containment, not prevention, and can generate false positives on legitimate cross-posting.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The vulnerability lives in NodeBB's ActivityPub inbound processing (see src/activitypub/mocks.js). ActivityPub objects carry an attributedTo property naming the author; in a correct implementation the server must confirm that attributedTo resolves to the same remote actor whose HTTP signature was verified. NodeBB instead passes attributedTo straight through as a uid in the object mock, and actors.assert silently drops bare numeric identifiers (filtering them out rather than re-deriving the correct uid). As a result a numeric value such as 1 is accepted verbatim as the local author id. This is a textbook CWE-345 (Insufficient Verification of Data Authenticity): the sender's authenticated identity is decoupled from the content's claimed authorship, so authenticity of the author field is never enforced.
Know when Nodebb gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N
Network and unauthenticated (PR:N: attacker uses their own valid remote signature, no local account); AC:H because federation must be enabled and a signature-passing remote actor is required; only integrity is impacted via author forgery, so C:N/A:N.
Primary rating from Vendor (VulnCheck).
CVSS VectorVendor: VulnCheck
Lifecycle Timeline
1DescriptionCVE.org
NodeBB does not bind the claimed author of an inbound ActivityPub object to the authenticated remote actor. The inbound middleware verifies the HTTP-signature actor and checks the origin of object.id, but never validates that attributedTo corresponds to the sender. In the object mock, attributedTo is used directly as a uid, and actors.assert silently ignores numeric identifiers (filtering them out without re-deriving the uid), so a federated remote actor can set attributedTo to a bare numeric value such as 1 and have the resulting post or private message created with that local uid as author, including the administrator account. This lets a remote attacker forge posts and direct messages attributed to arbitrary local users. Requires the ActivityPub/federation feature to be enabled.
Executive ViewAI
NodeBB's ActivityPub federation feature (CVE-2026-58593, CVSS 8.7) contains a flaw allowing remote attackers to forge posts and private messages attributed to any local user, including administrators, through inadequate source validation. Publicly available exploit code exists, creating immediate risk of admin account compromise and unauthorized content injection for all NodeBB instances with federation enabled. No vendor patch is currently available, requiring urgent interim mitigations.
No vendor-released patch identified at time of analysis. Interim mitigations: (1) Disable ActivityPub federation if not operationally essential-this eliminates attack surface entirely; (2) Restrict federation to pre-approved trusted remote instances using network firewall rules; (3) Enable comprehensive audit logging for all post/message creation and user attribution changes; (4) Conduct immediate forensic review of recent posts and messages attributed to administrative accounts; (5) Implement real-time alerts for administrative account modifications, permission changes, or sensitive actions.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.
A remote code execution (RCE) vulnerability in the xmlrpc.php endpoint of NodeBB Inc NodeBB forum software prior to v1.1
NodeBB Forum Software is powered by Node.js and supports either Redis, MongoDB, or a PostgreSQL database. Rated high sev
Nodebb is an open source Node.js based forum software. Rated high severity (CVSS 7.5), this vulnerability is remotely ex
Nodebb is an open source Node.js based forum software. Rated medium severity (CVSS 6.1), this vulnerability is remotely
NodeBB before version 1.14.3 has a bug introduced in version 1.12.2 in the validation logic that makes it possible to ch
NodeBB is Node.js based forum software. Rated critical severity (CVSS 9.8), this vulnerability is remotely exploitable,
NodeBB is an open source Node.js based forum software. Rated critical severity (CVSS 9.8), this vulnerability is remotel
NodeBB Forum Software is powered by Node.js and supports either Redis, MongoDB, or a PostgreSQL database. Rated critical
A persistent cross-site scripting (XSS) vulnerability in NodeBB v3.11.0 allows remote attackers to store arbitrary code
Nodebb is an open source Node.js based forum software. Rated medium severity (CVSS 5.0), this vulnerability is remotely
A vulnerability, which was classified as problematic, was found in NodeBB up to 2.5.7. Rated medium severity (CVSS 4.3),
In nodebb-plugin-blog-comments before version 0.7.0, a logged in user is vulnerable to an XSS attack which could allow a
EUVD-2026-41131
GHSA-8m27-grg5-27vj
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB