CVE-2023-6474VulnerabilityPublished 2 Dec 2023Updated 3 Jun 2025

CVE-2023-6474: PHPGurukul Nipah Virus Testing Management System · Cross-Site Request Forgery

Affects PHPGurukul Nipah Virus Testing Management SystemSource CVE Database V5

Not known to be exploited · CVSS 4.3 Medium.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.1 base score

4.3Medium

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

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

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

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: Required
Scope: Unchanged
Confidentiality: None
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: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
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: None: There is no loss of confidentiality within 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 2 Dec 2023
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
GitHubdhabaleshwar/niv_testing_csrf`pkg:github/dhabaleshwar/niv_testing_csrf`Other threats	Affected =1.0	Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

To mitigate this vulnerability, organizations should implement anti-CSRF tokens in all state-changing forms and requests within the Nipah Virus Testing Management System, ensuring that any request modifying data requires a valid, unpredictable token tied to the user's session. Additionally, validating the 'pid' parameter on the server side to ensure it matches expected formats and user permissions can reduce risk. Organizations should also enforce strict session management and consider implementing same-site cookie attributes to limit cross-origin requests. User education is critical to reduce the risk of social engineering attacks that could trigger CSRF exploits. Monitoring web server logs for unusual POST requests or unexpected parameter values can help detect attempted exploitation. Regular backups of critical data will aid recovery if integrity is compromised. Finally, engaging with the vendor or community for updates or patches is recommended to ensure timely remediation once available.

Description

A vulnerability has been found in PHPGurukul Nipah Virus Testing Management System 1.0 and classified as problematic. This vulnerability affects unknown code of the file manage-phlebotomist.php. The manipulation of the argument pid leads to cross-site request forgery. The attack can be initiated remotely. The exploit has been disclosed to the public and may be used. The identifier of this vulnerability is VDB-246640.

Impact

For European organizations, especially healthcare providers, laboratories, and public health agencies involved in infectious disease testing and management, this vulnerability poses a risk of unauthorized modification of phlebotomist-related data. Although the direct confidentiality and availability impacts are minimal, integrity compromise could lead to inaccurate test management, misallocation of resources, or administrative confusion. This could indirectly affect patient care quality and public health response effectiveness. Since the system is specialized and likely deployed in healthcare environments, exploitation could undermine trust in testing data and complicate outbreak management efforts. The requirement for user interaction means phishing or social engineering campaigns could be used to trigger the exploit, increasing risk in environments where users may not be trained to recognize such attacks. The medium severity score reflects these considerations but also indicates that the threat is not immediately critical. However, given the sensitive nature of healthcare data and operations, even moderate integrity issues warrant prompt attention.

Summary

CVE-2023-6474 is a Cross-Site Request Forgery (CSRF) vulnerability identified in version 1.0 of the PHPGurukul Nipah Virus Testing Management System, specifically within the manage-phlebotomist.php component. CSRF vulnerabilities occur when an attacker tricks an authenticated user into submitting a forged HTTP request, causing the application to perform unwanted actions on behalf of the user without their consent. In this case, the vulnerability arises from improper validation of the 'pid' parameter, which can be manipulated remotely to execute unauthorized state-changing operations. The vulnerability does not require prior authentication (PR:N), has low attack complexity (AC:L), and requires user interaction (UI:R), such as the victim clicking a malicious link or visiting a crafted webpage. The CVSS v3.1 base score is 4.3, indicating a medium severity level, with no impact on confidentiality or availability but a limited impact on integrity due to unauthorized changes that could be made to phlebotomist management data. No public exploits have been reported in the wild yet, and no patches have been officially released. The vulnerability is classified under CWE-352, which is a common web application security weakness related to CSRF attacks. Given the nature of the affected system—a specialized management system for Nipah virus testing—this vulnerability could allow attackers to manipulate critical healthcare workflow data, potentially disrupting testing operations or corrupting records.

CWE-352Cross-Site Request Forgery (CSRF) (opens in a new tab)
Compound weaknessLikelihood of exploit: MediumCWE Top 25 (2025): #3OWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
The web application does not, or cannot, sufficiently verify whether a request was intentionally provided by the user who sent the request, which could have originated from an unauthorized actor.
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
Ensure that the application is free of cross-site scripting issues (CWE-79), because most CSRF defenses can be bypassed using attacker-controlled script.
Architecture and Design
Generate a unique nonce for each form, place the nonce into the form, and verify the nonce upon receipt of the form. Be sure that the nonce is not predictable (CWE-330).
OWASP Cheat Sheets
REST Assessment (opens in a new tab)
REST Security (opens in a new tab)
Cross-Site Request Forgery Prevention (opens in a new tab)
Authorization Testing Automation (opens in a new tab)
Insecure Direct Object Reference Prevention (opens in a new tab)
OWASP ASVS 4.0.3
V13.2.3 (opens in a new tab)
V4.2.2 (opens in a new tab)
V13.3.2 (opens in a new tab)
Attack patterns
JSON Hijacking (aka JavaScript Hijacking) (opens in a new tab)
Cross-Domain Search Timing (opens in a new tab)
Cross Site Identification (opens in a new tab)
Cross Site Request Forgery (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

Affected software

Description

AI analysisMachine-generated, updated 3 Jul 2025, 18:24 UTC

WeaknessesCWE-352

Technical details

References

Community reviews

Related threats