CVE-2026-9013: Bogo (WordPress plugin) · Missing Authorization
Affects Bogo (WordPress plugin)Source CVE Database V5
Not known to be exploited · CVSS 4.3 Medium.
Data as of 3 Nov 2026, 22:58 UTC
- EPSS
- 0.4% chance of exploitation in 30 days – higher than 38% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:NExploitation evidence
Disclosed: evidence found.
CVE published 19 Jun 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 3 Nov 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| rocklobsterincBogo | Affected
| Fixed in– |
AI-suggested
Until a patch is available, restrict subscriber-level user permissions where possible and monitor for suspicious use of the bogo_rest_create_post_translation endpoint. Review and limit the number of users with contributor or higher roles to reduce risk. Follow updates from the vendor for an official fix.
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.
References
- wordfence.com/threat-intel/vulnerabilities/id/b04ba117-da4b-445e-99c2-69a5e4f34a65?source=cve (opens in a new tab)
- plugins.trac.wordpress.org/browser/bogo/tags/3.9.1/includes/rest-api.php (opens in a new tab)
- plugins.trac.wordpress.org/browser/bogo/tags/3.9.1/includes/rest-api.php (opens in a new tab)
- plugins.trac.wordpress.org/browser/bogo/tags/3.9.1/includes/post.php (opens in a new tab)
- plugins.trac.wordpress.org/browser/bogo/trunk/includes/rest-api.php (opens in a new tab)
- plugins.trac.wordpress.org/browser/bogo/trunk/includes/rest-api.php (opens in a new tab)
- plugins.trac.wordpress.org/browser/bogo/trunk/includes/post.php (opens in a new tab)
- github.com/rocklobster-in/bogo/pull/382/changes (opens in a new tab)
- plugins.trac.wordpress.org/changeset?sfp_email=&sfph_mail=&reponame=&old=3574263%40bogo&new=3574263%40bogo&sfp_email=&sfph_mail= (opens in a new tab)