CVE-2025-4587 MEDIUM

CVE-2025-4587: A/B Testing for WordPress <= 1.18.2 - Authenticated (Contributor+) Stored Cross-Site Scripting

Vendor Johnjamesjacoby
Product A/B Testing for WordPress
Weakness CWE-79 · XSS
Published June 27, 2025
Last update April 8, 2026

CVSS base score

6.4/10
Attack vector Network
Attack complexity Low
Privileges required Low
User interaction None
Confidentiality Low
Integrity Low

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N

What the vulnerability does

01Description

The A/B Testing for WordPress plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the plugin's 'ab-testing-for-wp/ab-test-block' block in all versions up to, and including, 1.18.2 due to insufficient input sanitization and output escaping on the 'id' parameter. This makes it possible for authenticated attackers, with contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.

Explanation of Vulnerability in Simple Terms

02Summary

The A/B Testing for WordPress plugin through version 1.18.2 contains a stored cross-site scripting (XSS) vulnerability. An authenticated user with low privileges can inject malicious scripts that execute in the browsers of other site users, including administrators. The vulnerability affects the plugin's scope across the site, allowing attackers to steal session tokens, modify content, or perform actions as higher-privileged users.

What an attacker can do

03Attacker Capabilities

Inject malicious scripts that run in other users' browsers and steal their session tokens or perform actions on their behalf.

Potential impact on your site

04Site Impact

Authenticated attackers can compromise administrator accounts and modify site content or settings without direct admin access.

Conditions required to exploit

05Prerequisites

Attacker must have a low-privilege WordPress account (e.g., subscriber or contributor role) and network access to the site.

Key dates

06Disclosure timeline

June 27, 2025 CVE published
April 8, 2026 Record updated