- Exploited
- No known exploitation
- Fix
- Fixed in 3.4.2
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 3.4.2.
- Last modified
- FIRST's estimate of the chance attackers exploit it in the next 30 days, updated daily.What do these mean? →
- 0.13% · 2nd percentile
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 0/100 · provisional
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
WP Event Manager, a WordPress plugin, has a flaw in one of its frontend forms that does not properly check ownership of the post IDs it processes. A logged-in user with a Subscriber account or higher can reassign authorship of arbitrary posts to themselves and force them to publish, exposing private or draft content; this requires the relevant frontend feature to be enabled.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
Read the original description
The WP Event Manager WordPress plugin before 3.4.2 does not properly validate ownership or the type of the user-supplied post identifiers processed by one of its frontend forms, allowing any user with a Subscriber account or above to reassign the authorship of arbitrary posts to themselves and to force them to be published. This results in content takeover and in the public disclosure of otherwise private or draft content, and requires the relevant frontend feature to be enabled.
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure?/25Unknown. No advisory context yet
- Reach?/20Unknown. No tracked technology or package matched
- Severity?/10Unknown. No CVSS score or vendor rating
- No patch0/5No signal
What would change the score
- Would score about 55 if added to CISA KEV
- Would score about 50 if CISA's SSVC rates exploitation active
- Would score about 22 if advisories confirm default setups are exposed
What to do
Upgrade to a fixed version: 3.4.2.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- Unknown WP Event Manager
fixed in 3.4.2
Evidence 1
- Exploit
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-16304
Is CVE-2026-16304 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
Which versions are affected by CVE-2026-16304?
WP Event Manager: before 3.4.2.Source: cve.now feed data
How do I fix CVE-2026-16304?
Upgrade to a fixed version: 3.4.2.Source: cve.now feed data