ActivitypubWordPress extension · Automattic
CVE-2026-4338
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 · uneditedThe ActivityPub WordPress plugin before 8.0.2 does not properly filter posts to be displayed, allowed unauthenticated users to access drafts/scheduled/pending posts
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 confidenceThe ActivityPub WordPress plugin before version 8.0.2 fails to properly filter posts based on publication status in its query logic. This broken access control allows unauthenticated (anonymous) users to retrieve and view content that has not yet been published, including draft, scheduled, and pending posts, via the plugin's API endpoints.
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
ActivitypubWordPress extension
< 8.0.2CVSS 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
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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.
-
Verify ActivityPub plugin is installedCheck WordPress plugins directory or wp-admin plugins page for the ActivityPub plugin by AutomatticAffected if ActivityPub plugin is not installed - not affected
-
Check installed versionView plugin details in WordPress admin plugins list or inspect the plugin header in the main plugin file to identify the version numberAffected if Installed version is less than 8.0.2 (vulnerable)
-
Confirm ActivityPub REST endpoint is accessibleAttempt to access the ActivityPub endpoint (typically /wp-json/activitypub/v1/ or similar endpoint path) without authentication using a browser or curlAffected if Endpoint returns HTTP 200 and exposes post data to unauthenticated requests
Environment is affected if the ActivityPub plugin version is below 8.0.2 and the ActivityPub endpoint is publicly accessible without authentication, allowing potential exposure of non-public post content.
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 · scoped8.0.2
Update the ActivityPub plugin to version 8.0.2 or later, which includes proper post status filtering to ensure only published content is accessible to unauthenticated users.
ActivityPub plugin version 8.0.2
- Log in to the WordPress admin dashboard
- Navigate to Plugins > Installed Plugins
- Find the ActivityPub plugin
- Click 'Update now' if an update is available, or manually update to version 8.0.2
- Verify the plugin version is now 8.0.2 or higher
- Test that unauthenticated visitors cannot access draft, scheduled, or pending posts
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Activitypub
Scoped from the published advisory
- Consultation1.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-4338 — 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-2026-4338 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