Skip to main content
Vulnerability Database/CVE-2024-34321

CVE-2024-34321: ProPhoenix Law RMS XSS Vulnerability

CVE-2024-34321 is a reflected cross-site scripting vulnerability in ProPhoenix Law RMS v2022.2403.3.101 that enables attackers to inject malicious scripts through the Notes.aspx endpoint. This article covers technical details, impact analysis, and mitigation strategies.

Published:

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

CVE-2024-34321 Overview

CVE-2024-34321 is a reflected cross-site scripting (XSS) vulnerability in ProPhoenix Law RMS v2022.2403.3.101. The flaw resides in the Notes.aspx endpoint, where the PageTitle and Notes parameters are reflected in the server response without proper output encoding. An unauthenticated attacker can craft a malicious URL that executes arbitrary JavaScript in the victim's browser session. ProPhoenix Law RMS is a records management system used by law enforcement agencies, which raises the sensitivity of session hijacking or credential theft against operator accounts.

Critical Impact

Attackers can execute arbitrary JavaScript in authenticated law enforcement operator sessions through a crafted link, enabling session theft and content manipulation [CWE-79].

Affected Products

  • ProPhoenix Law RMS v2022.2403.3.101
  • Notes.aspx endpoint (PageTitle parameter)
  • Notes.aspx endpoint (Notes parameter)

Discovery Timeline

  • 2026-10-13 - CVE-2024-34321 published to NVD
  • 2026-10-15 - Last updated in NVD database

Technical Details for CVE-2024-34321

Vulnerability Analysis

The vulnerability is a reflected XSS flaw in the Notes functionality of ProPhoenix Law RMS. User-controlled values passed through the PageTitle and Notes query parameters to Notes.aspx are returned to the browser without sufficient sanitization or contextual encoding. When a victim clicks a crafted link, the injected script executes under the application's origin.

Because the application manages law enforcement records, injected JavaScript can access authenticated sessions, exfiltrate case data visible to the operator, or submit requests against protected endpoints. The scope change in the CVSS vector reflects that the executed script can affect resources beyond the vulnerable component, such as other application pages loaded within the same browser session.

Additional background on this product line and related disclosures is available in the Sedric Louissaint research blog on ProPhoenix Law RMS.

Root Cause

The root cause is improper neutralization of input during web page generation [CWE-79]. The Notes.aspx handler reflects the PageTitle and Notes parameter values directly into the HTML response without HTML entity encoding or a Content Security Policy that would block inline script execution.

Attack Vector

Exploitation requires user interaction. An attacker crafts a URL to the vulnerable Notes.aspx endpoint with a malicious payload in the PageTitle or Notes parameter. The attacker then delivers the link through phishing, chat, or an embedded reference. When an authenticated operator loads the URL, the browser renders and executes the injected script in the application's context.

The vulnerability does not require authentication to trigger, but impact is highest when the victim already holds an authenticated session with the Law RMS application. No verified public exploit code is currently available for this CVE.

Detection Methods for CVE-2024-34321

Indicators of Compromise

  • HTTP GET or POST requests to Notes.aspx containing script tags, event handlers (onerror=, onload=), or encoded <script> sequences in the PageTitle or Notes parameters.
  • Unexpected outbound requests from operator browsers to attacker-controlled domains shortly after accessing a Notes URL.
  • Web server access logs showing abnormally long or URL-encoded query strings targeting the Notes.aspx endpoint.

Detection Strategies

  • Deploy web application firewall (WAF) rules that inspect query and body parameters sent to Notes.aspx for XSS payload patterns, including <script>, javascript:, and HTML event handler attributes.
  • Review IIS or reverse-proxy logs for requests to Notes.aspx with suspicious characters such as <, >, %3C, %3E, or onerror in the PageTitle and Notes parameters.
  • Correlate email gateway and proxy telemetry to identify delivery of URLs pointing to the Law RMS host with embedded parameter payloads.

Monitoring Recommendations

  • Enable detailed request logging on the ProPhoenix application server and forward logs to a centralized analytics platform for retention and query.
  • Monitor authenticated user sessions for anomalous behavior following link clicks, including unusual record access patterns or session token reuse from new IP addresses.
  • Alert on browser-reported CSP violations if a Content Security Policy is deployed in report-only mode as an interim control.

How to Mitigate CVE-2024-34321

Immediate Actions Required

  • Contact ProPhoenix support to confirm patch availability for v2022.2403.3.101 and schedule remediation.
  • Restrict external access to the Law RMS application through VPN or IP allow-listing until a fix is applied.
  • Brief operators on the risk of clicking unsolicited links that reference Notes.aspx or the application hostname.

Patch Information

No vendor advisory URL is published in the NVD record at the time of writing. Administrators should contact ProPhoenix directly through the ProPhoenix Law RMS product page to obtain a fixed build and verify remediation of the PageTitle and Notes parameter handling in Notes.aspx.

Workarounds

  • Deploy a WAF rule that blocks or sanitizes requests to Notes.aspx containing HTML metacharacters or JavaScript event handlers in the PageTitle and Notes parameters.
  • Enforce a strict Content Security Policy that disables inline script execution (script-src 'self') for the Law RMS application.
  • Enable the HttpOnly and Secure flags on session cookies to limit the impact of script-based session theft.
bash
# Example WAF rule (ModSecurity) blocking XSS payloads on Notes.aspx
SecRule REQUEST_URI "@contains /Notes.aspx" \
  "id:1003421,phase:2,deny,status:403,log,\
   chain,msg:'Potential XSS targeting CVE-2024-34321'"
  SecRule ARGS:PageTitle|ARGS:Notes \
    "@rx (?i)(<script|javascript:|onerror=|onload=|<svg)"

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

Experience the Most Advanced Cybersecurity Platform

See how the world’s most intelligent, autonomous cybersecurity platform can protect your organization today and into the future.