NVD / CVE Program· CNA CERT-PL

CVE-2025-30058: SQL injection in getPatientIdentifier function of PatientService.pl

MediumCVSS 6.9 · v4.0—No exploit No fix recorded

Noroxi assessment

Priority: Monitor (action score 27/100)

The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
Probability of exploitation in the next 30 days: 0.21% (FIRST EPSS).
Someone on the same network segment can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
According to the record, no fixed version is available yet.

Low priority for now. Update when a fix is released; follow the vendor's advisory.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

In the PatientService.pl service, the "getPatientIdentifier" function is vulnerable to SQL injection through the "pesel" parameter.

SQL injection

Published: Aug 27, 2025
Updated: Jun 17, 2026
EPSS: 0.2% · 12th percentile
CWE: CWE-89

Report tools

JSON

Action score

Monitor

Low priority for now.

CVSS: 27 / 40 · 6.9 / 10
CISA KEV: 0 / 30 · Not listed
EPSS: 0 / 30 · 0.2%

CISA SSVC decision

Exploitation: none
Automatable: no
Technical impact: partial

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD: —
CNA · CERT-PL: 6.9; NVD has not scored this yet; the score shown is the CNA’s.

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

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

Not in KEV: no record of exploitation in the wild
No public exploit code on record
No fixed version yet

If any of these changes, we'll tell you in the daily email digest.

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

—

Versions reported by the vendor

Affected version ranges reported by the assigning authority (CERT-PL). Independent of NVD's CPE analysis and usually ahead of it.

CGM CGM CLININET
- before 2024.MS4affected

Same product

cgm: all records

Other highest-scoring records for the same primary product.

CVE-2025-30054Local Privilege Escalation in CGM CLININET
37Monitor
CVE-2025-30050Remote Code Execution in CGM CLININET
37Monitor
CVE-2025-30047Remote Code Execution via Java Deserialization in CGM CLININET
37Monitor

Published before and after this one in the same product

← EarlierCVE-2025-30056Aug 27, 2025 · Calling system commands via RunCommand
37Monitor
← EarlierCVE-2025-30057Aug 27, 2025 · Authenticated RCE with uhcapache privileges in ConvertToPDF
37Monitor
Later →CVE-2025-30059Aug 27, 2025 · Authenticated SQL injection in PrepareCDExportJSON.pl
27Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

No fix version is recorded for this entry. Check the references for vendor advisories.

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

Maciej Kazulakfinder

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

CVE-2025-300590 days apartAuthenticated SQL injection in PrepareCDExportJSON.pl
27Monitor
CVE-2025-300600 days apartSQL injection in ReturnUserUnitsXML.pl via the UserID parameter
27Monitor
CVE-2025-300610 days apartSQL injection in utils/Reporter/OpenReportWindow.pl via the UserID parameter
27Monitor
CVE-2025-30062187 days apartSQL injection in CheckUnitCodeAndKey.pl
27Monitor

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

CVE-2025-300390 days apartMissing authentication in API returning a list of all active sessions
36Monitor
CVE-2025-300400 days apartMissing authentication in API returning request logs containing session IDs
36Monitor
CVE-2025-300410 days apartMissing authentication in APIs returning statistical data along with session IDs
36Monitor
CVE-2025-300370 days apartMissing authentication in APIs allowing data retrieval and modification
35Monitor

Not on record for this CVE: EPSS history · patch commit or PR link · public bounty program.

Technical details

Attack conditions

Someone on the same network segment can trigger it.
A low-privileged account is enough.
No user action is required.
No special conditions are required; it is repeatable.

If successful

Confidentiality
Integrity
Availability

Attack vector: Adjacent
Attack complexity: Low
Privileges required: Low
User interaction: None
Scope: X

Weakness class (CWE)

CWE-89 · Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')

CVSS vector

CVSS:4.0/AV:A/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

nvd-secondary

Root cause

The query text is built by concatenating user input. The database cannot tell where the data ends and the command begins.

The bug in code

The whole CWE-89 class

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

1const owner = req.query.owner;
2const rows = await db.query(
3  "SELECT * FROM files WHERE owner = '" + owner + "'"
4);

Fixed

1const owner = req.query.owner;
2const rows = await db.query(
3  "SELECT * FROM files WHERE owner = $1",
4  [owner]
5);

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

Attack patterns (CAPEC)

ATT&CK techniques

—

Change log (0)

No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.

References

cert.pl/en/posts/2025/08/CVE-2025-2313/

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records