What is the CVSS score of CVE-2026-2424?

CVE-2026-2424 has a CVSS 3.1 base score of 4.4 (Medium). CVSS vector: CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/C:L/I:L/A:N. EPSS exploitation probability: 0.0%.

Which versions of WordPress are affected by CVE-2026-2424?

Organizations using Reward Video Ad for WordPress should be aware of moderate risk from CVE-2026-2424, a cross-site scripting vulnerability rated CVSS 4.4.

How to fix or mitigate CVE-2026-2424?

Within 30 days: Identify affected systems running for WordPress is vulnerable to Stored Cross-Site Scripting v and apply vendor patches as part of regular patch cycle. Verify Content-Security-Policy and output encoding.

WordPress CVE-2026-2424

EUVD-2026-13993 MEDIUM

Cross-site Scripting (XSS) (CWE-79)

2026-03-21 Wordfence

GHSA-rgp4-7j5m-vg8m

WordPress XSS

4.4

CVSS 3.1 · NVD

Severity by source

NVD PRIMARY

4.4 MEDIUM

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

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

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

Attack Vector

Network

Attack Complexity

High

Privileges Required

High

User Interaction

None

Scope

Changed

Confidentiality

Low

Integrity

Low

Availability

None

Lifecycle Timeline

EUVD ID Assigned

Mar 21, 2026 - 04:00 euvd

EUVD-2026-13993

Analysis Generated

Mar 21, 2026 - 04:00 vuln.today

CVE Published

Mar 21, 2026 - 03:26 nvd

MEDIUM 4.4

DescriptionCVE.org

The Reward Video Ad for WordPress plugin for WordPress is vulnerable to Stored Cross-Site Scripting via admin settings in all versions up to, and including, 1.6. This is due to insufficient input sanitization and output escaping on plugin settings such as the 'Account ID', 'Message before the video', and color fields. This makes it possible for authenticated attackers, with Administrator-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.

AnalysisAI

The Reward Video Ad for WordPress plugin (all versions up to 1.6) contains a Stored Cross-Site Scripting (XSS) vulnerability in its admin settings due to insufficient input sanitization and output escaping on fields including Account ID, Message before the video, and color parameters. This allows authenticated administrators to inject arbitrary JavaScript that executes whenever any user accesses an affected page, potentially compromising site visitors. The vulnerability requires Administrator-level access to exploit, limiting the attack surface to high-privilege accounts, though once injected, the malicious scripts execute with no further user interaction required.

Technical ContextAI

The vulnerability is a classic Stored XSS (CWE-79: Improper Neutralization of Input During Web Page Generation) affecting the WordPress plugin ecosystem. The affected product is identified via CPE as cpe:2.3:a:applixir:reward_video_ad_for_wordpress:*:*:*:*:*:*:*:*, indicating all versions of the Applixir Reward Video Ad plugin are in scope up to version 1.6. The root cause lies in the plugin's settings handler (referenced at /inc/settings.php#L665 and /inc/class-applixir-restriction.php#L80 in the WordPress plugin repository) which accepts user input for configuration parameters like Account ID and message text without proper WordPress sanitization functions (sanitize_text_field, wp_kses_post) or escaping on output (wp_esc_attr, esc_html). When these unsanitized settings are rendered in the WordPress admin or front-end pages, attacker-controlled payloads execute in the context of the page.

RemediationAI

Update the Reward Video Ad for WordPress plugin to a patched version beyond 1.6 as soon as the vendor releases it; check the plugin repository and Wordfence advisories for patch availability. Until patching is possible, restrict Administrator-level access to only trusted users with multi-factor authentication enabled, conduct regular audits of admin accounts and their activity logs, and disable or remove the plugin from production if not actively used. Additionally, implement WordPress-wide input sanitization and output escaping best practices by reviewing plugin code and considering using security plugins such as Wordfence or Sucuri that can detect injected malicious scripts in the WordPress database. For sensitive WordPress installations, implement Content Security Policy (CSP) headers to limit the scope of injected scripts.