EUVD-2026-37983
GHSA-4vf9-6whq-7g9v
Severity by source
AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N
Network-accessible REST endpoint requires only a subscriber account (PR:L); impact is limited to reading private post text fields with no integrity or availability consequence.
Primary rating from Vendor (Wordfence).
CVSS VectorVendor: Wordfence
Lifecycle Timeline
3DescriptionCVE.org
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.
AnalysisAI
Sensitive information exposure in the Bogo WordPress plugin through version 3.9.1 allows authenticated users with subscriber-level access to extract the raw title, body content, excerpt, and password of any private, draft, or password-protected post by abusing the translation duplication endpoint. The REST API handler bogo_rest_create_post_translation enforced only a locale-access capability check, which all authenticated users can satisfy, and returned raw post field values in the API response without verifying whether the requestor had read or edit rights over the source content. No public exploit code or active exploitation (CISA KEV) is confirmed at time of analysis, though the attack path is straightforward for any authenticated WordPress user.
Technical ContextAI
The Bogo plugin (CPE: cpe:2.3:a:rocklobsterinc:bogo:*:*:*:*:*:*:*:*) provides multilingual translation support for WordPress by duplicating posts across locales via a REST API endpoint. The vulnerable function bogo_rest_create_post_translation (rest-api.php) clones a source post into a target locale and returned the duplicate's raw fields - title.raw, content.raw, excerpt.raw, and guid.raw - unconditionally in the JSON response. The authorization callback (rest-api.php:L31) only checked current_user_can('bogo_access_locale', $locale), a capability available to all authenticated users for the site's default locale. CWE-862 (Missing Authorization) is the root cause: the endpoint failed to verify that the requesting user held any capability over the source post (read, edit, or otherwise) before exposing its raw content. The fix (PR #382) adds a create_posts capability check in the auth callback and gates raw field population on edit_post capability for the newly created duplicate, and blocks non-published post duplication unless the user can edit the source post.
RemediationAI
Update the Bogo plugin to the version containing the fix from GitHub PR #382 and WordPress plugin repository changeset 3574263. An exact patched release version number is not independently confirmed from available data, but the fix is present in the plugin trunk (https://plugins.trac.wordpress.org/browser/bogo/trunk/includes/rest-api.php). Site administrators should update via the WordPress dashboard as soon as an updated version is published. The WordPress plugin repository changeset is available at https://plugins.trac.wordpress.org/changeset?sfp_email=&sfph_mail=&reponame=&old=3574263%40bogo&new=3574263%40bogo. As a compensating control prior to patching, access to the REST API endpoint bogo_rest_create_post_translation can be blocked at the WAF or web server layer for non-editor/non-admin roles, though this will break legitimate translation functionality for those users. Alternatively, restricting WordPress user registration to prevent untrusted subscriber accounts eliminates the low-privilege attack surface. Removing or disabling the Bogo plugin entirely is a drastic option that eliminates multilingual functionality.
More in Wordpress Plugin
View allThe Backup Migration plugin for WordPress is vulnerable to Remote Code Execution in all versions up to, and including, 1
The Hash Form - Drag & Drop Form Builder plugin for WordPress is vulnerable to arbitrary file uploads due to missing fil
Authentication bypass in the LiteSpeed Cache WordPress plugin (versions prior to 6.5.0.1) allows unauthenticated remote
The Simple File List plugin for WordPress through version 4.2.2 contains an unauthenticated remote code execution vulner
The SureTriggers WordPress plugin through version 1.0.82 contains a privilege escalation vulnerability that allows unaut
The Ninja Forms plugin before 2.9.42.1 for WordPress allows remote attackers to conduct PHP object injection attacks via
The Business Directory Plugin - Easy Listing Directories for WordPress plugin for WordPress is vulnerable to time-based
SQL injection in the NotificationX WordPress plugin (versions up to and including 2.8.2) allows unauthenticated remote a
The POST SMTP Mailer - Email log, Delivery Failure Notifications and Best Mail SMTP for WordPress plugin for WordPress i
The MasterStudy LMS WordPress Plugin - for Online Courses and Education plugin for WordPress is vulnerable to union base
The Email Subscribers by Icegram Express plugin for WordPress is vulnerable to SQL Injection via the ‘hash’ parameter in
Remote code execution in the WP Query Console WordPress plugin (versions up to and including 1.0) by Ajit Bohra allows u
Same weakness CWE-862 – Missing Authorization
View allSame technique Authentication Bypass
View allShare
External POC / Exploit Code
Leaving vuln.today