CVE-2025-6285VulnerabilityPublished 19 Jun 2025Updated 23 Jun 2025

CVE-2025-6285: PHPGurukul COVID19 Testing Management System · Cross Site Scripting

Affects PHPGurukul COVID19 Testing Management SystemSource CVE Database V5

Not known to be exploited · CVSS 5.3 Medium.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 4.0 base score

5.3Medium

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

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

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:P

Base metrics

Attack Vector: Network
Attack Complexity: Low
Attack Requirements: None
Privileges Required: None
User Interaction: Passive
Vulnerable system confidentiality: None
Vulnerable system integrity: Low
Vulnerable system availability: None
Subsequent system confidentiality: None
Subsequent system integrity: None
Subsequent system availability: None

Threat metrics

Exploit Maturity: POC

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

Attack Vector: Network: The vulnerable system is bound to the network stack and the set of possible attackers extends beyond the other options listed below, 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: The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
Attack Requirements: None: The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files of the vulnerable system to carry out an attack.
User Interaction: Passive: Successful exploitation of this vulnerability requires limited interaction by the targeted user with the vulnerable system and the attacker’s payload. These interactions would be considered involuntary and do not require that the user actively subvert protections built into the vulnerable system.
Vulnerable system confidentiality: None: There is no loss of confidentiality within the Vulnerable System.
Vulnerable system 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 to the Vulnerable System.
Vulnerable system availability: None: There is no impact to availability within the Vulnerable System.
Subsequent system confidentiality: None: There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.
Subsequent system integrity: None: There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.
Exploit Maturity: POC: Based on threat intelligence sources each of the following must apply: · Proof-of-concept is publicly available · No knowledge of reported attempts to exploit this vulnerability · No knowledge of publicly available solutions used to simplify attempts to exploit the vulnerability

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 19 Jun 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 2026-10-26.

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 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

Affected software

Product	Affected	Fixed in
PHPGurukul COVID19 Testing Management System	Affected =2021	Fixed in–

AI-suggested

1. Immediate implementation of input validation and output encoding on the 'q' parameter in /search-report-result.php to neutralize malicious scripts. Use established libraries or frameworks for sanitizing user input to prevent XSS. 2. Employ Content Security Policy (CSP) headers to restrict the execution of unauthorized scripts in the browser context. 3. Conduct a thorough code review of the entire application to identify and remediate other potential XSS or injection points. 4. Educate users, especially healthcare staff, about the risks of clicking on suspicious links and the importance of verifying URLs before accessing the system. 5. Monitor web server logs and application logs for unusual query patterns or repeated attempts to exploit the 'q' parameter. 6. If possible, upgrade to a patched version of the PHPGurukul COVID19 Testing Management System once available or apply vendor-provided patches promptly. 7. Implement multi-factor authentication (MFA) for user access to reduce the impact of session hijacking. 8. Segment the COVID19 Testing Management System network to limit exposure and lateral movement in case of compromise. 9. Regularly update and patch the underlying web server and PHP environment to reduce the attack surface.

Description

A vulnerability was found in PHPGurukul COVID19 Testing Management System 2021. It has been rated as problematic. This issue affects some unknown processing of the file /search-report-result.php. The manipulation of the argument q leads to cross site scripting. The attack may be initiated remotely. The exploit has been disclosed to the public and may be used.

Impact

For European organizations, especially healthcare providers and public health authorities using the PHPGurukul COVID19 Testing Management System, this vulnerability poses a risk to the confidentiality and integrity of sensitive health data. Exploitation could lead to unauthorized disclosure of patient information, manipulation of test results, or session hijacking of legitimate users. This undermines trust in public health systems and could disrupt COVID-19 testing workflows. Additionally, since the system is used to manage critical health data, successful attacks could facilitate further social engineering or phishing campaigns targeting healthcare personnel and patients. The medium severity rating suggests moderate risk, but the public disclosure of exploit details increases the urgency for mitigation. The impact is amplified in environments where the system is integrated with other healthcare IT infrastructure, potentially allowing lateral movement or data leakage. However, the lack of known active exploitation reduces immediate threat levels but does not eliminate future risk.

Summary

CVE-2025-6285 is a cross-site scripting (XSS) vulnerability identified in the PHPGurukul COVID19 Testing Management System version 2021. The vulnerability arises from improper input validation and sanitization of the 'q' parameter in the /search-report-result.php file. An attacker can manipulate this parameter to inject malicious scripts that execute in the context of the victim's browser. This vulnerability is remotely exploitable without requiring authentication, and user interaction is necessary for the attack to succeed, typically by tricking a user into clicking a crafted link or visiting a malicious page. The CVSS 4.0 base score is 5.3, indicating a medium severity level. The attack vector is network-based (AV:N), with low attack complexity (AC:L), no privileges required (PR:N), but requires user interaction (UI:P). The impact primarily affects the confidentiality and integrity of user data by potentially stealing session cookies, redirecting users, or performing unauthorized actions on behalf of the user. Availability impact is negligible. No known exploits are currently observed in the wild, but the exploit details have been publicly disclosed, increasing the risk of exploitation. The vulnerability does not involve any authentication bypass or privilege escalation but can be leveraged to target users of the system, potentially including healthcare workers and patients accessing COVID-19 test results or related sensitive information. Given the nature of the application, the vulnerability could facilitate phishing attacks or unauthorized data disclosure within healthcare environments managing COVID-19 testing data.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 23 Jun 2025, 19:40 UTC

Technical details

References

Community reviews

Related threats