dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2025-30058

MEDIUM · 6.9 CVSS v4.0 Published 2025-08-27
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
71/100
Remediation priority · Elevated
Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

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

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The PatientService.pl Perl service contains a SQL injection vulnerability in the getPatientIdentifier function where user-supplied input to the 'pesel' parameter is directly concatenated into SQL queries without proper sanitization or parameterized queries, allowing attackers to manipulate database queries.

MitigationReplace dynamic SQL query construction with parameterized queries/prepared statements in the getPatientIdentifier function, implement strict input validation on the pesel parameter, and apply least-privilege principles to database accounts.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Adjacent
Complexity
Low
Privileges
Low
Authentication
X
User interaction
None
Scope
X

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Locate PatientService.pl file
    Search the system for the PatientService.pl file using 'find / -name PatientService.pl 2>/dev/null' or check common application directories
    Affected if The file exists in the environment and contains the getPatientIdentifier function
  2. Examine getPatientIdentifier function
    Open PatientService.pl and locate the getPatientIdentifier sub-routine. Inspect how the 'pesel' parameter is handled
    Affected if The function exists and processes the 'pesel' parameter in SQL queries
  3. Check for unsafe SQL concatenation
    Within getPatientIdentifier, look for SQL queries where the pesel variable is directly concatenated (e.g., "SELECT ... WHERE pesel = $pesel" or "... '$pesel'") instead of using placeholders or bind variables
    Affected if The pesel parameter is directly interpolated into SQL strings without parameterization or escaping
  4. Verify service is accessible
    Check if PatientService.pl is running as a network service or exposed via web/CGI that accepts user input to the pesel parameter
    Affected if The service accepts external input to the vulnerable function

You are affected if PatientService.pl with the vulnerable getPatientIdentifier function exists in your environment and the pesel parameter is used in unsanitized SQL string concatenation rather than parameterized queries.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Replace dynamic SQL query construction with parameterized queries/prepared statements in the getPatientIdentifier function, implement strict input validation on the pesel parameter, and apply least-privilege principles to database accounts.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-30058 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-30058 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data