CVE-2025-7803
BaseFortify
Publication date: 2025-07-18
Last updated on: 2025-07-22
Assigner: VulDB
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| descreekert | wx-discuz | * |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-94 | The product constructs all or part of a code segment using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the syntax or behavior of the intended code segment. |
| 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-7803 is a cross-site scripting (XSS) vulnerability in the wx-discuz project affecting the validToken function in wx.php. The vulnerability occurs because the function directly outputs user-supplied input from the 'echostr' parameter without proper sanitization or neutralization. This allows an attacker to inject malicious scripts that execute in other users' browsers when they visit the affected page, potentially compromising the integrity of the web application. [1, 2]
How can this vulnerability impact me? :
This vulnerability can allow remote attackers to execute malicious scripts in the context of other users' browsers by manipulating the 'echostr' parameter. This can lead to unauthorized actions performed on behalf of users, session hijacking, or other malicious activities that compromise data integrity. The attack requires some user interaction and can be initiated remotely without authentication. [1, 2]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by searching for HTTP requests or URLs that access the wx.php file with the echostr parameter, which is vulnerable to XSS. One suggested method is to use Google hacking techniques to find URLs containing "wx.php". On your network or system, you can monitor web server logs or use tools like curl or wget to test the endpoint. For example, you can run a command like: curl -G 'http://targetsite/wx.php' --data-urlencode 'echostr=<script>alert(1)</script>' and observe if the script is reflected in the response without sanitization, indicating vulnerability. [2, 1]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include replacing the affected product with an alternative, as no known countermeasures or patches are currently available. Additionally, you can implement input validation and output sanitization on the echostr parameter to neutralize malicious scripts. Applying web application firewalls (WAF) rules to block suspicious payloads targeting wx.php may also help reduce risk until a fix is available. [2, 1]