CVE-2025-30060
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 ReturnUserUnitsXML.pl service, the "getUserInfo" function is vulnerable to SQL injection through the "UserID" 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 confidenceSQL injection vulnerability in the getUserInfo function of ReturnUserUnitsXML.pl service. The UserID parameter is not properly sanitized before being used in SQL queries, allowing an attacker to inject malicious SQL commands.
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 the ReturnUserUnitsXML.pl scriptSearch the web server document root, CGI bin directory, or application directories for the file ReturnUserUnitsXML.plAffected if The script is present in the environment and publicly accessible
-
Verify the getUserInfo function is exposedExamine the ReturnUserUnitsXML.pl script source code and confirm the getUserInfo subroutine is defined and callable via HTTP requestAffected if The getUserInfo function exists and can be invoked through the web service endpoint
-
Confirm UserID parameter acceptanceSend a test HTTP request to the ReturnUserUnitsXML.pl endpoint with a UserID parameter (e.g., ?UserID=test) and observe if the application processes itAffected if The UserID parameter is accepted and processed by the service without immediate rejection
-
Check if database queries use unsanitized UserIDReview the getUserInfo function source code to determine if UserID is directly interpolated into SQL queries without parameterized queries, input validation, or escapingAffected if The code constructs SQL queries by directly concatenating the UserID parameter value into the query string
-
Determine authentication requirementsTest whether the vulnerable endpoint is accessible without authentication or requires valid user credentialsAffected if The getUserInfo function can be reached without authentication or with low-privilege user access
The environment is affected if ReturnUserUnitsXML.pl with an accessible getUserInfo function that accepts a UserID parameter is present and the code directly uses that parameter in SQL queries without sanitization or parameterized queries.
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 dataImplement parameterized queries (prepared statements) for all SQL operations involving the UserID parameter, or use an input validation layer to sanitize user-supplied values before database interaction.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-30060 — 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-30060 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