Severity by source
AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Primary rating from Vendor (WPScan) · only source for this CVE.
CVSS VectorVendor: WPScan
Lifecycle Timeline
7DescriptionCVE.org
The ActivityPub WordPress plugin before 8.0.2 does not properly filter posts to be displayed, allowed unauthenticated users to access drafts/scheduled/pending posts
AnalysisAI
Improper access control in the ActivityPub WordPress plugin before 8.0.2 exposes draft, scheduled, and pending posts to unauthenticated remote users, resulting in confidentiality breach. This information disclosure vulnerability (CVSS 7.5) allows network-based attackers to access unpublished content without authentication or user interaction. Publicly available exploit code exists, though no confirmed active exploitation (not in CISA KEV). EPSS score of 0.02% (6th percentile) suggests low current exploitation probability despite POC availability, but SSVC framework marks it as automatable with partial technical impact.
Technical ContextAI
The ActivityPub plugin implements the ActivityPub protocol for WordPress, enabling federated social networking capabilities. This vulnerability stems from insufficient access control validation when filtering posts for external display. The plugin fails to properly enforce WordPress's built-in post status checks (draft, scheduled, pending) before exposing content through the ActivityPub API endpoints. The affected product is identified as 'cpe:2.3:a:unknown:activitypub' covering all versions prior to 8.0.2. While no specific CWE classification was assigned, this represents a classic broken access control issue where authorization checks are missing or improperly implemented at the API boundary, allowing unauthorized information retrieval from restricted content repositories.
RemediationAI
Upgrade the ActivityPub WordPress plugin to version 8.0.2 or later immediately to remediate this vulnerability. The vendor-released patch version 8.0.2 addresses the improper access control issue by implementing proper post status filtering before content exposure through ActivityPub endpoints. Administrators should access the WordPress plugin management interface and update ActivityPub through the standard update mechanism. For detailed vulnerability information and confirmation of the fix, consult the WPScan vulnerability database entry at https://wpscan.com/vulnerability/50f68395-72fc-4f99-8e6d-6aa90cc640b5/ and the NVD record at https://nvd.nist.gov/vuln/detail/CVE-2026-4338. If immediate patching is not feasible, temporary workarounds include disabling the ActivityPub plugin until upgrade is possible, or restricting network access to the WordPress installation using web application firewall rules that block unauthorized access to ActivityPub API endpoints. Review server logs for suspicious access patterns to draft/scheduled content URLs to determine if exploitation occurred prior to patching.
More in Activitypub
View allThe ActivityPub WordPress plugin before 1.0.0 does not escape user metadata before outputting them in mentions, which co
The ActivityPub WordPress plugin before 1.0.0 does not sanitize and escape some data from post content, which could allo
The ActivityPub WordPress plugin before 1.0.0 does not ensure that post contents to be displayed are public and belong t
The ActivityPub WordPress plugin before 1.0.0 does not ensure that post titles to be displayed are public and belong to
Same technique Information Disclosure
View allShare
External POC / Exploit Code
Leaving vuln.today
EUVD-2026-20058
GHSA-v6vj-m59r-f4gf