CVE-2026-8626 MEDIUM

CVE-2026-8626: SponsorMe <= 0.5.2 - Reflected Cross-Site Scripting via PHP_SELF Parameter

Vendor Owencutajar
Product SponsorMe
Weakness CWE-79 · XSS
Published May 20, 2026
Last update May 20, 2026

CVSS base score

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

CVSS vector

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

What the vulnerability does

01Description

The SponsorMe plugin for WordPress is vulnerable to Reflected Cross-Site Scripting via PHP_SELF Parameter in all versions up to, and including, 0.5.2 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that execute if they can successfully trick a user into performing an action such as clicking on a link. The PHP_SELF value is reflected in two separate locations within the vulnerable function — a form action attribute and an anchor href attribute — both of which can be exploited by appending a crafted payload to the wp-admin/admin.php URL path.

Explanation of Vulnerability in Simple Terms

02Summary

SponsorMe versions 0.5.2 and earlier contain a cross-site scripting (XSS) vulnerability that allows attackers to inject malicious scripts into web pages viewed by other users. The vulnerability requires user interaction—typically clicking a malicious link—and can affect users across different parts of the application. An attacker needs no authentication to exploit this flaw.

What an attacker can do

03Attacker Capabilities

Inject malicious JavaScript that runs in other users' browsers and steals session data or performs actions on their behalf.

Potential impact on your site

04Site Impact

Users' accounts and data are at risk if they interact with attacker-crafted links; site reputation may suffer if users report malicious behavior.

Conditions required to exploit

05Prerequisites

Victim must click a malicious link or visit an attacker-controlled page that triggers the vulnerability.

Key dates

06Disclosure timeline

May 20, 2026 CVE published
May 20, 2026 Record updated

Related vulnerabilities

08Related CVE