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

CVE-2025-6286: PHPGurukul COVID19 Testing Management System · Open Redirect

Affects PHPGurukul COVID19 Testing Management SystemSource CVE Database V5

Not known to be exploited · CVSS 5.1 Medium.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 4.0 base score

5.1Medium

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

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

CVSS:4.0/AV:N/AC:L/AT:N/PR:L/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: Low
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: Low: The attacker requires privileges that provide basic capabilities that are typically limited to settings and resources owned by a single low-privileged user. Alternatively, an attacker with Low privileges has the ability to access only non-sensitive resources.
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

To mitigate this vulnerability, European organizations should implement the following specific measures: 1) Validate and sanitize the 'q' parameter in /search-report-result.php to ensure it only allows safe, internal URLs or predefined redirect targets. 2) Implement strict allowlists for redirect URLs to prevent arbitrary external redirection. 3) Employ Content Security Policy (CSP) headers to restrict the domains that can be loaded or navigated to from the application. 4) Educate users and staff about the risks of phishing and the signs of suspicious redirects, particularly in the context of COVID19 testing portals. 5) Monitor web server logs for unusual redirect patterns or spikes in traffic to suspicious domains. 6) If possible, update or patch the PHPGurukul COVID19 Testing Management System once an official fix is released. 7) Consider deploying Web Application Firewalls (WAFs) with rules to detect and block open redirect attempts targeting the vulnerable parameter. 8) Review and enhance authentication and session management controls to reduce the impact if credentials are compromised through phishing. These targeted actions go beyond generic advice by focusing on the specific vulnerable parameter and the operational context of the affected system.

Description

A vulnerability classified as problematic has been found in PHPGurukul COVID19 Testing Management System 2021. Affected is an unknown function of the file /search-report-result.php. The manipulation of the argument q leads to open redirect. It is possible to launch the attack remotely. The exploit has been disclosed to the public and may be used.

Impact

For European organizations using the PHPGurukul COVID19 Testing Management System 2021, this vulnerability could have several impacts. Primarily, it could facilitate phishing attacks by redirecting legitimate users to malicious websites, potentially leading to credential compromise or malware infections. Since the system handles sensitive health data related to COVID19 testing, any loss of user trust or successful phishing could result in reputational damage and reduced user engagement with critical health services. While the vulnerability does not directly compromise data confidentiality or system availability, the indirect effects of social engineering attacks could lead to unauthorized access if users are tricked into divulging credentials. Additionally, healthcare organizations are subject to strict data protection regulations such as GDPR; any incident stemming from this vulnerability could trigger regulatory scrutiny and potential fines. The medium severity rating suggests that while the vulnerability is not critical, it still poses a tangible risk, especially in the context of healthcare services where user trust and data integrity are paramount.

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