How severe is CVE-2024-4257?

CVE-2024-4257 has a CVSS score of 6.3/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by CVE-2024-4257?

Affected package information for CVE-2024-4257 is not yet fully mapped. Check the official advisory links for details.

How do I fix CVE-2024-4257?

No fixed version has been published for CVE-2024-4257 yet. Monitor the advisory for updates, apply mitigations recommended by the vendor, and use O3 Security to track when a fix becomes available in your stack.

Is CVE-2024-4257 actively exploited in the wild?

No public exploit code has been indexed for CVE-2024-4257 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2024-4257?

CVE-2024-4257 has an EPSS (Exploit Prediction Scoring System) score of 92.1%, placing it in the 100th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. A score above 50% indicates significantly elevated exploitation risk — immediate patching is strongly recommended.

What type of vulnerability is CVE-2024-4257?

CVE-2024-4257 is classified as SQL Injection (CWE-89). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

Which products and versions are affected by CVE-2024-4257?

CVE-2024-4257 affects bluenettechnology clinical browsing system (1 version, e.g. 1.2.1). Check the affected-products list on this page against your deployed version to confirm exposure.

Is there exploit tooling available for CVE-2024-4257?

A Nuclei detection template exists for CVE-2024-4257, meaning automated scanners can fingerprint it. Public exploit tooling significantly increases real-world risk — prioritize patching and ensure detection coverage. Exploit tooling should only ever be used in isolated, authorized testing environments.

When was CVE-2024-4257 published, and has it been updated?

CVE-2024-4257 was published on April 27, 2024 and was last updated on October 15, 2025. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

CVE-2024-4257: Clinical Browsing System SQL Injection (Medium 6…

EPSS Exploitation Probability

via FIRST.org ↗

92.1%probability of exploitation in next 30 days

Very High Risk100th percentile0.00%

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Description

A vulnerability was found in BlueNet Technology Clinical Browsing System 1.2.1. It has been classified as critical. This affects an unknown part of the file /xds/deleteStudy.php. The manipulation of the argument documentUniqueId leads to sql injection. It is possible to initiate the attack remotely. The exploit has been disclosed to the public and may be used. The identifier VDB-262149 was assigned to this vulnerability.

Affected Products

1 product · 1 configurations

Application

clinical browsing systembluenettechnology

1 version

1.2.1

Frequently Asked Questions

A vulnerability was found in BlueNet Technology Clinical Browsing System 1.2.1. It has been classified as critical. This affects an unknown part of the file /xds/deleteStudy.php. The manipulation of the argument documentUniqueId leads to sql injection. It is possible to initiate the attack remotely. The exploit has been disclosed to the public and may be used. The identifier VDB-262149 was assigned to this vulnerability.

O3 Security · Impact-Aware SCA

Is CVE-2024-4257 in your stack?

O3 detects CVE-2024-4257 across dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my stack How O3 SCA works