CVE-2026-3743
Remote XSS in YiFang CMS 2.0.5 app/db/admin Component
Publication date: 2026-03-08
Last updated on: 2026-04-29
Assigner: VulDB
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| yifangcms | yifang | 2.0.5 |
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. |
| 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. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
[{'type': 'paragraph', 'content': 'CVE-2026-3743 is a stored Cross-Site Scripting (XSS) vulnerability found in YiFang CMS version 2.0.5. It affects the update function in the file app/db/admin/D_singlePageGroup.php, specifically the handling of the "name" parameter in the /admin/singlePageGroup interface.'}, {'type': 'paragraph', 'content': 'The vulnerability occurs because the "name" field is taken directly from user input and stored in the database without any filtering or sanitization. This allows an attacker to inject malicious JavaScript code that is persistently stored.'}, {'type': 'paragraph', 'content': 'When a user later accesses the single-page category list, the malicious script executes in their browser, leading to a cross-site scripting attack.'}, {'type': 'paragraph', 'content': 'The attack can be launched remotely and requires some user interaction. There is a publicly available proof-of-concept exploit.'}] [1, 2, 3]
How can this vulnerability impact me? :
[{'type': 'paragraph', 'content': 'This vulnerability can allow attackers to execute arbitrary JavaScript code in the browsers of users who visit the affected single-page category list in YiFang CMS 2.0.5.'}, {'type': 'paragraph', 'content': "Potential impacts include theft of user session cookies, defacement of web pages, redirection to malicious sites, or other malicious actions performed in the context of the victim's browser."}, {'type': 'paragraph', 'content': 'Because the malicious code is stored persistently, every user accessing the vulnerable page is at risk.'}, {'type': 'paragraph', 'content': 'The vulnerability requires some user interaction but can be exploited remotely, making it a significant security risk for websites using this CMS version.'}] [1, 2, 3]
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 checking for the presence of the vulnerable endpoint and testing the 'name' parameter in the /admin/singlePageGroup interface for stored cross-site scripting (XSS) payloads."}, {'type': 'paragraph', 'content': 'One method to identify vulnerable targets is using Google dorking with the query: inurl:app/db/admin/D_singlePageGroup.php.'}, {'type': 'paragraph', 'content': "To test manually, you can send a crafted POST request to the endpoint with a malicious payload in the 'name' parameter and observe if the script is stored and executed when accessing the single-page category list."}, {'type': 'list_item', 'content': 'Example curl command to test injection:'}, {'type': 'list_item', 'content': "curl -X POST 'http://target-site/admin/singlePageGroup?callback=ajaxRs' -F 'name=2<svg onload=alert(1)>'"}, {'type': 'paragraph', 'content': 'If the alert or script executes when viewing the single-page category list, the system is vulnerable.'}] [2, 3]
What immediate steps should I take to mitigate this vulnerability?
[{'type': 'paragraph', 'content': 'Currently, there are no known vendor patches or mitigations available for this vulnerability.'}, {'type': 'paragraph', 'content': 'Immediate mitigation steps include considering replacing YiFang CMS version 2.0.5 with an alternative product that is not vulnerable.'}, {'type': 'paragraph', 'content': "Additionally, restricting access to the vulnerable endpoint and implementing web application firewall (WAF) rules to detect and block malicious payloads targeting the 'name' parameter may help reduce risk."}, {'type': 'paragraph', 'content': 'Monitoring for suspicious POST requests to /admin/singlePageGroup and sanitizing inputs at the application level, if possible, are recommended interim measures.'}] [2]