Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

New CVE Detected

CVE-2026-58593 – Unauthenticated Identity Spoofing / Post & Message Forgery – NodeBB up to v4.13.2

Be the first to know when new zero-days emerge:

Summary

CVE-2026-58593 is a high-severity identity spoofing vulnerability (CVSS 7.5) in NodeBB, an open-source Node.js-based internet forum platform. The flaw resides in NodeBB’s ActivityPub/federation inbound middleware and allows any unauthenticated remote federated actor to forge posts and private messages attributed to arbitrary local users — including the administrator account — without any credentials on the target instance. A public proof-of-concept exploit is referenced in the CVE record.

Technical details

  • Root cause: The ActivityPub inbound middleware correctly verifies the HTTP-signature actor and validates the origin of object.id, but never checks that the attributedTo field in the received object corresponds to the authenticated sending actor. The attributedTo value is used directly as a local user ID (uid) when constructing the object mock. Additionally, actors.assert silently discards numeric identifiers rather than re-deriving the canonical uid, allowing the spoofed value to pass through unchallenged. (CWE-345: Insufficient Verification of Data Authenticity; CWE-290: Authentication Bypass by Spoofing)
  • Trigger conditions: An attacker-controlled federated ActivityPub server sends an inbound Create activity with attributedTo set to a bare integer (e.g., 1, the default administrator uid) instead of a proper actor URI.
  • Attack vector: Fully remote and unauthenticated (AV:N, PR:N, UI:N, AC:L). Exploitable from any external ActivityPub-speaking server that the victim NodeBB instance will accept federation with.
  • Impact: Posts and direct messages are created on the target NodeBB instance bearing the identity of the targeted local user. Impersonating the administrator account enables spreading malicious links under a trusted authority, targeted phishing of community members, social-engineering-based privilege escalation, and significant reputational damage to the affected forum.
  • Prerequisite: The ActivityPub/federation feature must be enabled on the target instance. This is a non-default feature first introduced in NodeBB v4.

Affected software

  • NodeBB v4.13.2 and earlier versions of the v4 branch with the ActivityPub/federation feature enabled
  • NodeBB v3.x and v2.x branches do not include the ActivityPub feature and are not affected

Severity

CVSS v3.1 Base Score: 7.5 (HIGH)
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N

Mitigation and recommended actions

  • Patch: No patched NodeBB release has been published as of the CVE publication date (July 1, 2026). Monitor the NodeBB GitHub releases and official community announcements for a security update and apply it immediately upon availability.
  • Immediate workaround: If your deployment does not require ActivityPub federation, disable the feature in your NodeBB Admin Control Panel under Settings → ActivityPub. Disabling the feature removes the vulnerable inbound processing pathway.
  • Network mitigation: If disabling the feature is not possible, consider restricting inbound federation traffic to known, trusted federated peers at the network or reverse-proxy level to reduce your exposure surface while awaiting a patch.

IONIX Status

The IONIX research team is tracking ongoing exploitation attempts and recommends immediate patching. Potentially affected assets are outlined in this post.

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge