CVE-2026-9013 Bogo <= 3.9.1 - Missing Authorization to Authenticated (Subscriber+) Sensitive Information Exposure via REST API
Authenticated subscribers can expose sensitive content from private or password-protected posts via the Bogo plugin's REST API translation endpoint.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- None listed
What is CVE-2026-9013?
CVE-2026-9013 is a medium-severity missing authorization vulnerability in rocklobsterinc Bogo, published on 19 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Official description
The Bogo plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and including, 3.9.1 via the bogo_rest_create_post_translation. This makes it possible for authenticated attackers, with subscriber-level access and above, to extract the raw title, content, excerpt, and password of any private, draft, or password-protected post by triggering its duplication via the translation endpoint and reading the returned title.raw, content.raw, and excerpt.raw fields of the duplicated post. This vulnerability is exploitable against posts written in a non-default locale, as authenticated subscribers can request a translation into the site's default locale to pass the locale-only permission gate. While subscribers can trigger the endpoint, this is only impactful at the Contributor-level as they can actually read the duplicated content.
Weakness: CWE-862
Which versions are affected by CVE-2026-9013?
How do I fix CVE-2026-9013?
No fix has been published for CVE-2026-9013 yet. Limit exposure of the affected software until one is available.
Upgrade, and check permissions on every request on the server, not only in the interface. More about Missing authorization.
Is CVE-2026-9013 being exploited?
There is no known exploitation of CVE-2026-9013 in the wild and no public exploit code.
Sources
Also known as GHSA-4vf9-6whq-7g9v.