CVE-2026-1320
Stored XSS in Secure Copy Plugin via X-Forwarded-For Header
Publication date: 2026-02-12
Last updated on: 2026-02-12
Assigner: Wordfence
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| wordfence | secure_copy_content_protection | to 4.9.8 (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 Secure Copy Content Protection and Content Locking plugin for WordPress is vulnerable to Stored Cross-Site Scripting (XSS) via the 'X-Forwarded-For' HTTP header in all versions up to and including 4.9.8.
This vulnerability exists because the plugin does not properly sanitize input or escape output, allowing unauthenticated attackers to inject arbitrary web scripts.
These injected scripts execute whenever a user accesses a page containing the malicious code.
How can this vulnerability impact me? :
This vulnerability can allow attackers to execute arbitrary scripts in the context of the affected website.
- Attackers can steal user session cookies or credentials.
- They can perform actions on behalf of users without their consent.
- It can lead to defacement or redirection to malicious sites.
- Overall, it compromises the confidentiality and integrity of user interactions with the website.
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