CVE-2025-65233
Reflected XSS in SLiMS sysconfig.inc.php Allows Remote Script Execution
Publication date: 2025-12-17
Last updated on: 2025-12-17
Assigner: MITRE
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| slims | slims | 9.6.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. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability is a reflected cross-site scripting (XSS) issue in the SLiMS (slims9_bulian) system before version 9.6.0. It arises from improper handling of the PHP_SELF server variable in the index.php/sysconfig.inc.php file. An attacker can craft a malicious URL that injects arbitrary JavaScript code, which is then executed in the victim's browser when they visit the URL. This happens because user input from the URL is not properly validated or escaped before being included in the web page. [2]
How can this vulnerability impact me? :
This vulnerability can allow remote attackers to execute arbitrary JavaScript in the browsers of users who visit a crafted URL. This can lead to session hijacking, theft of sensitive information, defacement of the website, or redirection to malicious sites. Essentially, it compromises the security and trustworthiness of the affected web application and can negatively impact users' privacy and security. [2]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by testing the affected SLiMS system for reflected XSS in the URL path, specifically by injecting a crafted URL similar to the example: /index.php/'"--><script>alert('gembel')</script></index.php?p=profil-singkat and observing if arbitrary JavaScript executes (e.g., an alert popup). There are no specific commands provided, but manual testing via a browser or automated scanning tools targeting reflected XSS in URL parameters can be used. [2]
What immediate steps should I take to mitigate this vulnerability?
No specific mitigation or patch details are provided in the available resources. Immediate steps generally include restricting access to the vulnerable endpoint, applying input validation and output encoding on the affected parameters, or temporarily disabling the affected functionality until a patch is available. [2]