CVE-2026-3946
Cross-Site Scripting in PHPEMS 11.0 /index.php Remotely Exploitable
Publication date: 2026-03-11
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 |
|---|---|---|
| phpems | phpems | 11.0 |
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-3946 is a stored Cross-Site Scripting (XSS) vulnerability found in PHPEMS version 11.0. It occurs in the file /index.php with the parameter ask=app-ask, specifically through manipulation of the askcontent argument.'}, {'type': 'paragraph', 'content': 'The vulnerability arises because the input sanitization functions, including tidyHtml and purify, fail to filter out malicious script tags like <script>. Additionally, backend processing reverses escaping and decoding, allowing injected scripts to be stored and executed when viewed by an administrator.'}, {'type': 'paragraph', 'content': "This flaw allows an attacker to inject malicious JavaScript code remotely, which can execute in the context of the administrator's browser when they view the submitted content."}] [2, 3, 4]
How can this vulnerability impact me? :
This vulnerability can lead to the execution of malicious scripts in the browser of an administrator or other users who view the injected content.
Exploitation can result in theft of sensitive information such as user cookies, which may allow attackers to hijack sessions and compromise user accounts.
Because the attack is stored, the malicious payload persists on the server and can affect multiple users over time.
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': 'The vulnerability can be detected by testing the affected parameter `askcontent` in the URL `/index.php?ask=app-ask` for cross-site scripting (XSS) payloads. Specifically, submitting a payload such as `<script>alert(document.cookie)</script>` in the question content and observing if it executes when viewed by an administrator can confirm the presence of the vulnerability.'}, {'type': 'paragraph', 'content': 'Detection involves submitting crafted input to the web application and monitoring the response or behavior in the administrator interface. Since the vulnerability is stored XSS, it requires submitting data and then viewing it in the admin panel.'}, {'type': 'paragraph', 'content': 'Suggested commands or steps include using curl or browser-based tools to submit the payload, for example:'}, {'type': 'list_item', 'content': 'Use curl to submit a question with XSS payload: curl -X POST -d "args[askcontent]=<script>alert(document.cookie)</script>&other_params=values" http://target/index.php?ask=app-ask'}, {'type': 'list_item', 'content': 'Then, log in as an administrator and visit the question management page (`/index.php?ask-master-ask`) to check if the script executes.'}, {'type': 'paragraph', 'content': 'Because the vulnerability requires user interaction and viewing in the admin interface, automated network detection is limited; manual testing of the web interface is recommended.'}] [3]
What immediate steps should I take to mitigate this vulnerability?
No specific countermeasures or mitigations have been identified for this vulnerability in the provided information.
The suggested immediate step is to consider replacing PHPEMS with an alternative product that does not have this vulnerability.
Additionally, restricting administrative access and monitoring for suspicious activity can help reduce risk until a fix or patch is available.