CVE-2026-1841
Stored XSS in PixelYourSite WordPress Plugin Allows Script Injection
Publication date: 2026-02-13
Last updated on: 2026-04-08
Assigner: Wordfence
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| pixel_your_site | pixel_your_site | to 11.2.0 (inc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-79 | The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
The vulnerability exists in the PixelYourSite – Your smart PIXEL (TAG) & API Manager plugin for WordPress, affecting all versions up to and including 11.2.0. It is a Stored Cross-Site Scripting (XSS) vulnerability caused by insufficient input sanitization and output escaping of the 'pysTrafficSource' and 'pys_landing_page' parameters.
This flaw allows unauthenticated attackers to inject arbitrary web scripts into pages. These malicious scripts execute whenever a user accesses the injected page, potentially compromising user security.
How can this vulnerability impact me? :
This vulnerability can lead to unauthorized execution of malicious scripts in the context of the affected website. Since the attack is stored, any user visiting the compromised page may have these scripts executed in their browser without their knowledge.
- Potential impacts include theft of user credentials or session tokens.
- Manipulation or defacement of website content.
- Redirection of users to malicious sites.
- Loss of user trust and damage to the website's reputation.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
I don't know
How can this vulnerability be detected on my network or system? Can you suggest some commands?
I don't know
What immediate steps should I take to mitigate this vulnerability?
I don't know