CVE-2025-67620
BaseFortify
Publication date: 2026-01-22
Last updated on: 2026-01-29
Assigner: Patchstack
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| cleversoft | anon | to 2.2.10 (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?
CVE-2025-67620 is a medium priority Cross Site Scripting (XSS) vulnerability in the WordPress Anon Theme versions up to and including 2.2.10. It allows an unauthenticated attacker to inject malicious scripts—such as redirects, advertisements, or other HTML payloads—into a website. These scripts execute when visitors access the compromised site. Exploitation requires user interaction, such as clicking a malicious link, visiting a crafted page, or submitting a form. [1]
How can this vulnerability impact me? :
This vulnerability can impact you by allowing attackers to execute malicious scripts on your website, potentially leading to unauthorized redirects, display of unwanted advertisements, theft of user data, or other malicious actions. It compromises the security and integrity of your website and can harm your users by exposing them to malicious content. [1]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
Detection of this reflected XSS vulnerability can be done by testing the Anon Theme (version <= 2.2.10) for injection points where malicious scripts can be reflected. Since no official fix is available, using web vulnerability scanners or manual testing with crafted URLs containing typical XSS payloads (e.g., <script>alert(1)</script>) can help identify the issue. Specific commands are not provided in the resources, but tools like curl or browser-based testing with payloads in URL parameters can be used to detect reflected XSS. [1]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include applying the Patchstack mitigation rule that blocks attacks targeting this vulnerability until an official patch is released. Additionally, restricting user input, implementing web application firewalls (WAF) with rules to detect and block XSS payloads, and educating users to avoid clicking suspicious links can help reduce risk. [1]