VulnerabilityPublished 17 Nov 2025

CVE-2024-46335: PHPGurukul Complaint Management System · Cross-site Scripting

Source CVE Database V5

Not known to be exploited · CVSS 4.6 Medium.

Data as of 26 Oct 2026, 13:47 UTC

CVSS 3.1 base score

4.6Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.2% chance of exploitation in 30 days – higher than 11% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:L/I:L/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: Low
User Interaction: Required
Scope: Unchanged
Confidentiality: Low
Integrity: Low
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
User Interaction: Required: Successful exploitation of this vulnerability requires a user to take some action before the vulnerability can be exploited.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
Integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 17 Nov 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

AI-suggested

Implement strict input validation and sanitization on the fromdate and todate parameters to ensure only valid date formats are accepted, rejecting or encoding any unexpected characters.
Apply proper output encoding (e.g., HTML entity encoding) before reflecting user input in the web page to prevent script execution.
Restrict access to the complaint management system and sensitive reports to trusted and authenticated users only, minimizing the attack surface.
Employ Content Security Policy (CSP) headers to limit the execution of unauthorized scripts in browsers.
Conduct regular security code reviews and penetration testing focusing on input handling and XSS vulnerabilities.
Monitor logs and user activity for suspicious behavior indicative of exploitation attempts.
If possible, upgrade to a patched version once available or apply vendor-provided fixes promptly.
Educate users about phishing and social engineering risks that could facilitate exploitation via user interaction.

Description

CVE-2024-46335 is a medium severity Cross Site Scripting (XSS) vulnerability found in PHPGurukul Complaint Management System 2.0, specifically in the fromdate and todate parameters of the between-date-userreport.php script. The flaw allows an authenticated user to inject malicious scripts due to insufficient input sanitization, potentially leading to limited confidentiality and integrity impacts. Exploitation requires user interaction and privileges, and no known exploits are currently reported in the wild. The vulnerability does not affect system availability. European organizations using this complaint management system may face risks of session hijacking or data manipulation if exploited. Mitigation involves implementing strict input validation and output encoding on the affected parameters and restricting access to trusted users. Countries with higher adoption of PHPGurukul products or similar PHP-based complaint systems, such as the UK, Germany, and France, are more likely to be impacted. Given the medium CVSS score of 4.

Impact

For European organizations using PHPGurukul Complaint Management System 2.0, this vulnerability could lead to unauthorized disclosure of sensitive information such as session cookies or user data, potentially enabling account takeover or data manipulation. Although the impact is limited to confidentiality and integrity, exploitation could undermine trust in complaint handling processes and expose personal or organizational information. Since the vulnerability requires authentication and user interaction, the risk is somewhat mitigated but still significant in environments with many users or where phishing/social engineering could be used to trigger the exploit. The absence of availability impact means service disruption is unlikely. However, regulatory frameworks like GDPR emphasize protecting personal data, so even limited data exposure could have compliance implications. Organizations relying on this system should assess their exposure and prioritize remediation to avoid reputational damage and potential legal consequences.

Summary

CVE-2024-46335 identifies a Cross Site Scripting (XSS) vulnerability in the PHPGurukul Complaint Management System version 2.0. The vulnerability resides in the fromdate and todate parameters within the between-date-userreport.php script, where user-supplied input is not properly sanitized or encoded before being reflected back in the web page. This allows an authenticated attacker with at least limited privileges to inject malicious JavaScript code that executes in the context of other users’ browsers. The CVSS v3.1 vector (AV:N/AC:L/PR:L/UI:R/S:U/C:L/I:L/A:N) indicates that the attack can be performed remotely over the network with low attack complexity, requires privileges (authenticated user), and user interaction (clicking a crafted link or submitting a form). The impact affects confidentiality and integrity to a limited extent, as the attacker could steal session tokens, manipulate displayed data, or perform actions on behalf of the victim user. There is no impact on availability. No patches or known exploits are currently available, but the vulnerability is publicly disclosed and should be addressed promptly. The underlying weakness corresponds to CWE-79, which is a common web application security flaw related to improper neutralization of input during output encoding.

CWE-79Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') (opens in a new tab)
Base weaknessLikelihood of exploit: HighCWE Top 25 (2025): #1OWASP Top 10 A05:2025: Injection (opens in a new tab)
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.
Architecture and Design · Libraries or Frameworks
Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
Implementation · Architecture and Design
Understand the context in which your data will be used and the encoding that will be expected. This is especially important when transmitting data between different components, or when generating outputs that can contain multiple encodings at the same time, such as web pages or multi-part mail messages.
Architecture and Design · Implementation · Attack Surface Reduction
Understand all the potential areas where untrusted inputs can enter your software: parameters or arguments, cookies, anything read from the network, environment variables, reverse DNS lookups, query results, request headers, URL components, e-mail, files, filenames, databases, and any external systems that provide…
OWASP Cheat Sheets
Cross Site Scripting Prevention (opens in a new tab)
DOM based XSS Prevention (opens in a new tab)
Injection Prevention (opens in a new tab)
Abuse Case (opens in a new tab)
Deserialization (opens in a new tab)
OWASP ASVS 4.0.3
V5.3.3 (opens in a new tab)
V1.5.1 (opens in a new tab)
Attack patterns
XSS Using MIME Type Mismatch (opens in a new tab)
DOM-Based XSS (opens in a new tab)
Reflected XSS (opens in a new tab)
Stored XSS (opens in a new tab)
Cross-Site Scripting (XSS) (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Description

AI analysisMachine-generated, updated 24 Nov 2025, 19:28 UTC

WeaknessesCWE-79

Technical details

References

Community reviews

Related threats