CVE-2025-30059
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 · uneditedIn the PrepareCDExportJSON.pl service, the "getPerfServiceIds" function is vulnerable to SQL injection.
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 · moderate confidenceA SQL injection vulnerability exists in the getPerfServiceIds function of PrepareCDExportJSON.pl. Attackers can exploit this by injecting malicious SQL statements through unsanitized input parameters processed by this function, potentially allowing unauthorized database access, data exfiltration, or database manipulation.
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 checksWork through these to decide whether this CVE applies to you.
-
Locate PrepareCDExportJSON.plSearch the filesystem for the file named PrepareCDExportJSON.pl. Check common application directories, web root folders, or any installation paths related to the application using this script.Affected if The file is not found, the vulnerability does not apply to your environment.
-
Find the getPerfServiceIds functionOpen PrepareCDExportJSON.pl and locate the getPerfServiceIds function definition. Identify the function boundaries and the SQL query construction logic within it.Affected if The function does not exist in your version of the file.
-
Examine SQL query constructionReview how the function builds SQL queries. Look for string concatenation or interpolation where user-supplied parameters are directly inserted into SQL statements (for example, "SELECT * FROM table WHERE id = " . $param).Affected if The function constructs SQL queries by concatenating or interpolating variables directly into SQL strings without sanitization.
-
Check input handlingIdentify all input sources to getPerfServiceIds (query parameters, form inputs, environment variables, or other function arguments). Verify whether these inputs undergo any validation, escaping, or sanitization before being used in SQL queries.Affected if Input parameters are used directly in SQL queries without being passed through escaping functions, validation checks, or input sanitization routines.
-
Verify query preparation methodLook for the use of parameterized queries (prepare statements), bound parameters, or database abstraction methods that separate SQL structure from data values. Check for patterns like $dbh->prepare() with placeholders (?) or similar parameterized query approaches.Affected if The function does not use parameterized queries or prepared statements; it uses raw SQL execution with direct variable interpolation.
If PrepareCDExportJSON.pl exists and its getPerfServiceIds function builds SQL queries by directly inserting unsanitized input into SQL strings without parameterized queries, the environment is affected by CVE-2025-30059.
Generated from the published advisory. Verify against your own configuration.
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 dataRefactor the getPerfServiceIds function to use parameterized queries (prepared statements) or implement proper input validation and escaping for all database interactions.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-30059 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-30059 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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