CVE-2025-61224
BaseFortify
Publication date: 2025-10-06
Last updated on: 2025-10-08
Assigner: MITRE
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| dokuwiki | dokuwiki | * |
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-61224 is a reflected Cross-Site Scripting (XSS) vulnerability in DokuWiki's search user interface. It occurs because the namespace selector in the advanced search tools does not properly escape user-supplied input, allowing an attacker to inject malicious scripts. These scripts are then reflected back and executed in the victim's browser without requiring authentication. [1]
How can this vulnerability impact me? :
This vulnerability can allow remote attackers to execute arbitrary scripts in the context of a victim's browser. This can lead to theft of sensitive information, session hijacking, or performing actions on behalf of the user without their consent, potentially compromising user accounts and data. [1]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
Detection of this vulnerability can be done by testing the search user interface of DokuWiki for reflected Cross-Site Scripting (XSS) via the 'q' parameter or namespace selector in the advanced search tools. You can use tools like curl or a web vulnerability scanner to send crafted requests containing script payloads in the 'q' parameter and observe if the payload is reflected unescaped in the response. For example, a curl command to test might be: curl -v 'http://your-dokuwiki-site/doku.php?q=<script>alert(1)</script>'. If the script tags are reflected unescaped in the response, the vulnerability is present. [1]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include updating DokuWiki to a version where this vulnerability is fixed, as reported in the GitHub issue. If an update is not immediately possible, restrict access to the search interface or disable the advanced search tools temporarily to prevent exploitation. Additionally, implement web application firewall (WAF) rules to block requests containing suspicious script payloads in the 'q' parameter or namespace selector inputs. [1]