CVE-2026-8424

Remove Yellow BGBOX <= 1.0 - Cross-Site Request Forgery

Published May 20, 2026 CVSS 3.1 · 4.3 Medium EPSS < 1% KEV · Not listed
Description
The Remove Yellow BGBOX plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 1.0. This is due to missing or incorrect nonce validation on the 'rybb_api_settings' page. This makes it possible for unauthenticated attackers to reset the plugin's stored settings by overwriting its configuration via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.

Analysis

AI-generated

Technical impact

The Remove Yellow BGBOX WordPress plugin does not enforce proper nonce validation on the "rybb_api_settings" page, allowing a Cross‑Site Request Forgery attack. An unauthenticated attacker can craft a forged request that, if a logged‑in administrator follows a malicious link, will reset or overwrite the plugin’s stored configuration. Because the plugin’s settings can affect site behavior, this could lead to configuration changes that break site functionality or expose sensitive data, even though it does not directly provide code execution or data exfiltration. The weakness maps to CWE‑352, a classic CSRF flaw.

Affected Systems

All WordPress installations that include the Remove Yellow BGBOX plugin from jay_patel, in any version up to and including 1.0 – the range of affected releases is explicitly stated as "<= 1.0". Administrators using the deprecated plugin should note that the vulnerability applies to every site that permits the "rybb_api_settings" endpoint to be accessed while an administrative session is active.

Risk and Exploitability

The CVSS score is 4.3, indicating a moderate impact. EPSS data is unavailable and the vulnerability is not listed in CISA’s KEV catalog, suggesting no widespread active exploitation is documented. However, the attack vector is straightforward: a forged HTTP request to the vulnerable page can be induced by tricking an administrator to click a link. Consequently, the risk remains tangible for sites that actively use the plugin and have administrators who can be deceived.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade the Remove Yellow BGBOX plugin to a version newer than 1.0 that implements proper nonce validation on the settings page.
  • If an update is not immediately feasible, disable or delete the plugin to eliminate the vulnerable administrative endpoint.
  • Enforce stricter user authentication practices (e.g., multi‑factor authentication) and educate site administrators to avoid clicking suspicious links, as mitigation of the CSRF flaw also relies on user vigilance.

Generated by OpenCVE AI on May 20, 2026 at 03:24 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
First Time appeared Jay Patel
Jay Patel remove Yellow Bgbox
Wordpress
Wordpress wordpress
Vendors & Products Jay Patel
Jay Patel remove Yellow Bgbox
Wordpress
Wordpress wordpress
Type Values Removed Values Added
Description The Remove Yellow BGBOX plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 1.0. This is due to missing or incorrect nonce validation on the 'rybb_api_settings' page. This makes it possible for unauthenticated attackers to reset the plugin's stored settings by overwriting its configuration via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.
Title Remove Yellow BGBOX <= 1.0 - Cross-Site Request Forgery
Weaknesses CWE-352
References
Metrics cvssV3_1

{'score': 4.3, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N'}

Weaknesses
  • CWE-352

    Cross-Site Request Forgery (CSRF)

Sources

Status
PUBLISHED
Assigner
Wordfence
Published
Updated
May 20, 2026, 5:17 PM
Reserved
May 12, 2026, 5:50 PM
Status
Deferred
Published
May 20, 2026, 2:16 AM
Modified
Jul 23, 2026, 8:10 PM