code-projects Record Management System Offices offices.php cross site scripting

The primary impact of CVE-2023-7135 is the potential for cross-site scripting (XSS) attacks. An attacker can inject arbitrary JavaScript code into the Record Management System by manipulating the 'officename' parameter in the 'offices.php' file. This malicious script can then execute in the context of a user's browser, allowing the attacker to steal cookies, redirect users to phishing sites, or deface the application. The vulnerability is remotely exploitable, meaning an attacker does not need to be authenticated to exploit it. Given the public disclosure of this vulnerability, it is highly likely that attackers are actively scanning for and exploiting vulnerable instances.

Organizations using Record Management System version 1.0 are at risk. Specifically, those with publicly accessible instances of the system or those that handle sensitive user data are particularly vulnerable. Shared hosting environments where multiple users share the same Record Management System instance are also at increased risk.

• generic web: Use curl to test the /main/offices.php endpoint with a crafted payload like officename="><script>alert(1)</script>. Check the response for the alert box.

curl 'http://your-record-management-system/main/offices.php?officename="><script>alert(1)</script>'

• generic web: Examine access and error logs for suspicious requests containing <script> tags or other XSS payloads targeting the officename parameter. • generic web: Review response headers for any unusual content or redirects that might indicate XSS activity.

1. 2023-12-28Disclosure

   disclosure

1. Réservé2023-12-28
2. Publiée2023-12-28
3. Modifiée2024-08-02
4. EPSS mis à jour2026-04-02

The recommended mitigation for CVE-2023-7135 is to immediately upgrade to version 1.0.1 of the Record Management System. This version contains a fix for the XSS vulnerability. If upgrading is not immediately possible, consider implementing input validation and output encoding on the 'officename' parameter in 'offices.php' to sanitize user input. Web application firewalls (WAFs) configured to detect and block XSS payloads can also provide a temporary layer of protection. After upgrading, confirm the fix by attempting to inject a simple XSS payload (e.g., <script>alert(1)</script>) into the 'officename' parameter and verifying that the script does not execute.