CVE-2020-36932
BaseFortify
Publication date: 2026-01-25
Last updated on: 2026-02-02
Assigner: VulnCheck
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| seacms | seacms | 11.1 |
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-2020-36932 is a stored cross-site scripting (XSS) vulnerability in SeaCMS version 11.1. It exists in the 'checkuser' parameter of the admin settings page, where attackers can inject malicious JavaScript code. This injected code is stored by the application and executed in the browsers of users who load the affected page, potentially allowing attackers to perform unauthorized actions or steal sensitive information like cookies or session data. [2, 3]
How can this vulnerability impact me? :
This vulnerability can impact you by allowing attackers to execute malicious JavaScript in your browser when you access the affected admin settings page. This can lead to theft of session cookies, hijacking of user sessions, unauthorized actions performed on behalf of the user, and potential compromise of sensitive data within the application. [2, 3]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by sending a crafted POST request to the admin settings page endpoint `/SEACMS111/5f9js3/admin_safe.php?action=setting` with a malicious payload in the `checkuser` parameter, such as `"><ScRiPt>alert(document.cookie)</ScRiPt>`. Monitoring for such suspicious POST requests or unexpected JavaScript execution in the admin interface can help identify exploitation attempts. Specific commands would involve using tools like curl or Burp Suite to send the payload and observe if it is stored and executed. For example, a curl command to test might be: `curl -X POST -d "checkuser=\"><ScRiPt>alert(document.cookie)</ScRiPt>" https://your-seacms-site/SEACMS111/5f9js3/admin_safe.php?action=setting`. [2]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include restricting access to the admin settings page to trusted users only, applying input validation and sanitization on the `checkuser` parameter to prevent script injection, and updating SeaCMS to a version later than 11.1 where this vulnerability is fixed. Additionally, monitoring and blocking suspicious POST requests targeting the vulnerable endpoint can reduce risk until a patch is applied. [2, 3]