CVE-2026-32844
Reflected XSS in XinLiangCoder php_api_doc list_method.php
Publication date: 2026-03-20
Last updated on: 2026-04-14
Assigner: VulnCheck
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| xinliangcoder | php_api_doc | to 2019-03-24 (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?
[{'type': 'paragraph', 'content': 'CVE-2026-32844 is a reflected cross-site scripting (XSS) vulnerability in the XinLiangCoder php_api_doc project, specifically in the file list_method.php. The vulnerability occurs because the GET request parameter "f" is not properly sanitized before being output to the web page. This allows remote attackers to inject and execute arbitrary JavaScript code in the victim\'s browser by crafting a malicious URL with unsanitized input.'}] [1]
How can this vulnerability impact me? :
[{'type': 'paragraph', 'content': "Exploitation of this vulnerability can lead to session hijacking, credential theft, or malware distribution within the context of the affected application. Attackers can execute arbitrary JavaScript in a victim's browser, potentially compromising user accounts and sensitive information."}] [1]
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?
[{'type': 'paragraph', 'content': 'This vulnerability can be detected by monitoring HTTP GET requests to the vulnerable application, specifically looking for requests to list_method.php that include the parameter "f" with suspicious or malicious JavaScript code.'}, {'type': 'paragraph', 'content': 'One way to detect exploitation attempts is to analyze web server logs or use network monitoring tools to identify URLs containing the "f" parameter with potentially unsafe input.'}, {'type': 'list_item', 'content': 'Use grep or similar command-line tools to search web server access logs for suspicious patterns, for example:'}, {'type': 'list_item', 'content': "grep -i 'list_method.php' /var/log/apache2/access.log | grep 'f='"}, {'type': 'list_item', 'content': 'Use web application security scanners or proxy tools (like OWASP ZAP or Burp Suite) to test the list_method.php endpoint by injecting typical XSS payloads into the "f" parameter and observing if the input is reflected unsanitized.'}] [1]
What immediate steps should I take to mitigate this vulnerability?
[{'type': 'paragraph', 'content': 'Immediate mitigation steps include sanitizing and properly encoding the input received through the "f" parameter in list_method.php to prevent execution of arbitrary JavaScript.'}, {'type': 'paragraph', 'content': 'If you maintain the affected application, update or patch the code to neutralize the input before outputting it to the page.'}, {'type': 'paragraph', 'content': 'As a temporary measure, consider implementing web application firewall (WAF) rules to block requests containing suspicious scripts or patterns in the "f" parameter.'}, {'type': 'paragraph', 'content': 'Additionally, educate users to avoid clicking on suspicious links and monitor for unusual activity that may indicate exploitation attempts.'}] [1]