WordPress security changelog
MEDIUM CVE-2026-8424 Deferred

Remove Yellow BGBOX: Cross-site request forgery

Remove Yellow BGBOX is affected by cross-site request forgery. The vulnerable path is reachable without authentication. Exploitation relies on a signed-in privileged user submitting an attacker-controlled request. The published affected range is <= 1.0.

CVE / CNA score 4.3 CVSS 3.1 · security@wordfence.com
NVD score Pending NVD has not published its own CVSS assessment.
Component
Remove Yellow BGBOX
Plugin slug
remove-yellow-bgbox
Affected
<= 1.0
Safe version
See mitigation notes
Published
May 20, 2026
Weakness
CWE-352 — Cross-Site Request Forgery (CSRF)

This CVE was published May 20, 2026 and is one of 1 known issue for this plugin.

Update, patch or deactivate.

No fixed release is identified. Update Remove Yellow BGBOX when a release after 1.0 becomes available; until then, disable and remove it when the site's risk warrants.

No confirmed safe version is listed. Consider a vendor-supported patch or temporarily restricting the affected functionality while you assess the risk.

Deactivate only when warranted by your risk profile, or when advised by your hosting provider in the limited circumstances where the vulnerability cannot otherwise be mitigated. If you’re unsure which action is appropriate, contact Fused or your hosting provider for guidance.

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

CVE / CNA vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N

Primary and upstream sources