CVE-2025-7858
BaseFortify
Publication date: 2025-07-20
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 |
|---|---|---|
| phpgurukul | apartment_visitors_management_system | 1.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?
CVE-2025-7858 is a Stored Cross-Site Scripting (XSS) vulnerability in PHPGurukul Apartment Visitors Management System version 1.0. It occurs because the 'adminname' parameter submitted via a POST request to /admin-profile.php is not properly sanitized or encoded before being stored and displayed. This allows attackers to inject malicious JavaScript code that executes in the browsers of users who view the affected page, including administrators. [1, 2, 3]
How can this vulnerability impact me? :
This vulnerability can allow attackers to execute arbitrary JavaScript in the browsers of users who load the affected page. Potential impacts include theft of cookies or session tokens, performing Cross-Site Request Forgery (CSRF)-like attacks, privilege escalation if an administrator views the malicious content, exfiltration of sensitive data, and redirection of users to malicious websites. [2, 3]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by checking if the /admin-profile.php page of the PHPGurukul Apartment Visitors Management System version 1.0 improperly handles the 'adminname' parameter submitted via HTTP POST requests. One practical method is to use Google dorking with queries like 'inurl:admin-profile.php' to identify potentially vulnerable targets. Additionally, testing the POST parameter 'adminname' by injecting benign script payloads and observing if the input is reflected and executed in the HTML response can confirm the presence of the vulnerability. Network monitoring tools can be used to capture POST requests to /admin-profile.php and analyze the 'adminname' parameter for suspicious script content. Specific commands might include using curl or wget to send crafted POST requests, for example: curl -X POST -d "adminname=<script>alert(1)</script>" http://target/admin-profile.php and then checking the response or the page rendering for script execution. [2, 1]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include replacing the affected product with an alternative, as no known countermeasures or mitigations have been documented. Additionally, restricting access to the /admin-profile.php page, applying web application firewall (WAF) rules to block malicious payloads targeting the 'adminname' parameter, and monitoring for suspicious POST requests can help reduce risk. Implementing input validation and output encoding on the 'adminname' parameter to neutralize malicious scripts is recommended but may require code changes. Since the vulnerability allows remote exploitation without authentication, limiting network exposure of the affected system is also advised. [2]