CVE-2025-60118
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 · uneditedImproper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in Potenzaglobalsolutions PGS Core pgs-core allows SQL Injection.This issue affects PGS Core: from n/a through <= 5.9.0.
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 confidenceSQL injection vulnerability in Potenzaglobalsolutions PGS Core allows attackers to inject malicious SQL commands via unsanitized user inputs. This affects all versions of PGS Core up to and including 5.9.0. The high CVSS score of 8.5 indicates potential for significant data exposure or 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
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- None
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:L
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.
-
Confirm PGS Core installationIdentify if Potenzaglobalsolutions PGS Core is present in your environment by checking application metadata, installed packages, web application banners, or software inventory recordsAffected if PGS Core by Potenzaglobalsolutions is installed
-
Determine installed versionLocate the version identifier for PGS Core (check application configuration files, about pages, version headers, or software inventory) and compare against the affected rangeAffected if Version is 5.9.0 or lower
-
Identify accessible user input interfacesMap all web forms, API endpoints, search fields, login mechanisms, or other interfaces that accept user input within the PGS Core applicationAffected if Any user-accessible input fields exist that interact with the database
-
Inspect database query implementationReview application code or configuration to determine how user inputs are handled in database queries - look for direct string concatenation versus parameterized queriesAffected if User inputs are concatenated directly into SQL queries without parameterization or input sanitization
-
Check application logs for SQL injection attemptsReview application and database logs for suspicious SQL syntax in user input fields, unusual error messages, or evidence of injection patternsAffected if Logs show SQL injection patterns or exploitation attempts
You are affected if PGS Core version 5.9.0 or lower is installed and user input fields are accessible without proper SQL injection protections.
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 dataRemediate by implementing parameterized queries or prepared statements for all database interactions, applying strict input validation, and limiting database account privileges to least privilege principles.
- Consultation4.0 h
- Implementation16.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,960.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-60118 — 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-60118 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