CVE-2025-68871
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 |
|---|---|---|
| nocreativity | dooodl | to 2.3.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?
CVE-2025-68871 is a medium severity Reflected Cross-Site Scripting (XSS) vulnerability in the WordPress Dooodl Plugin versions up to 2.3.0. It allows an attacker to inject malicious scripts, such as redirects or advertisements, that execute when site visitors access compromised pages. Exploitation requires user interaction, like clicking a malicious link or visiting a crafted page, and no authentication is needed to initiate the attack. [1]
How can this vulnerability impact me? :
This vulnerability can lead to attackers executing malicious scripts in the context of the affected website, potentially redirecting users, displaying unwanted advertisements, stealing session information, or performing other harmful actions. This can compromise user trust, lead to data theft, and damage the website's reputation. [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 monitoring for suspicious HTTP requests containing malicious script payloads targeting the Dooodl plugin pages. Since exploitation involves user interaction with crafted URLs or forms, inspecting web server logs for unusual query parameters or payloads with script tags may help. Additionally, using web vulnerability scanners configured to test for reflected XSS on the affected plugin endpoints can assist in detection. Specific commands are not provided in the resources. [1]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include applying the Patchstack mitigation rule provided to block attacks targeting this vulnerability until an official patch is released. Users should implement this mitigation immediately to protect their websites. Since no official fixed plugin version is available as of the publication date, applying this rule is the recommended action. [1]