CVE-2025-22300

PixelYourSite – Your smart PIXEL (TAG) Manager <= 10.0.1.2 - Cross-Site Request Forgery

2025-01-06 00:00
Dhabaleshwar Das

Strategic Overview

Status
Patched in 10.0.2
Affected Plugin
PixelYourSite – Your smart PIXEL (TAG) & API Manager
Affected Version
<= 10.0.1.2
CVSS
4.3Medium
Weakness type
CWE-352 · Cross-Site Request Forgery (CSRF)
CVE
CVE-2025-22300
View all PixelYourSite – Your smart PIXEL (TAG) & API Manager vulnerabilities

At a glance

CVE-2025-22300 is a medium-severity Cross-Site Request Forgery (CSRF) vulnerability in the PixelYourSite WordPress plugin, affecting versions <= 10.0.1.2. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 10.0.2; sites on affected versions should update now. Disclosed January 2025, reported by Dhabaleshwar Das.

Vulnerability Overview

The PixelYourSite – Your smart PIXEL (TAG) Manager plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to, and including, 10.0.1.2. This is due to missing or incorrect nonce validation on the init() function. This makes it possible for unauthenticated attackers to modify settings via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.

Technical Analysis

The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site.

CWE-352: Cross-Site Request Forgery (CSRF)

PixelYourSite <= 10.0.1.2 carries this weakness at init(), and reaching it takes a caller who can reach the endpoint. Cross-site request forgery abuses the fact that browsers attach a victim's cookies to any request, so a state-changing action that only checks who you are, not whether you meant to act, can be triggered from another site.

An attacker who gets a logged-in user to load a crafted page can perform that action as them, with the impact scaling to whatever the victim's role is allowed to do. For PixelYourSite the fix is 10.0.2: builds <= 10.0.1.2 are affected, anything from 10.0.2 onward is not.

Remediation

Update to version 10.0.2, or a newer patched version

How does WordSec protect against this?

The attempt arrives as an ordinary request to PixelYourSite: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: PixelYourSite 10.0.2 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2025-22300https://www.wordfence.com/threat-intel/vulnerabilities/id/996c2843-158c-475a-874e-c5af00347d8chttps://nvd.nist.gov/vuln/detail/CVE-2025-22300

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C