CVE-2025-25403
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 · uneditedSlims (Senayan Library Management Systems) 9 Bulian V9.6.1 is vulnerable to SQL Injection in admin/modules/master_file/coll_type.php.
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 confidenceSlims 9 Bulian V9.6.1 contains a SQL Injection vulnerability in the admin/modules/master_file/coll_type.php component. The vulnerability allows unauthenticated attackers (or authenticated admin users) to inject malicious SQL queries through user input in this file, potentially allowing full database compromise, data exfiltration, or remote code execution in some configurations.
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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
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.
-
Identify SLiMS installation versionLocate the version file or footer in your SLiMS installation (commonly version.php, README, or admin about page) and record the installed version numberAffected if The installed version is 9.6.1 or earlier (including 9.6.0, 9.5.x, or older 9.x releases)
-
Verify coll_type.php existsCheck for the presence of the file admin/modules/master_file/coll_type.php in your SLiMS web root directoryAffected if The file exists in your installation, indicating the vulnerable component is present
-
Check admin module exposureDetermine whether the /admin/ directory is accessible from untrusted networks or the internet (check web server configuration, firewall rules, or network ACLs)Affected if The admin module is exposed to unauthenticated or untrusted network access
-
Review application authentication stateCheck if your SLiMS admin panel requires authentication for all users, or if anonymous/guest access is enabled in the admin areaAffected if Anonymous or weak authentication is configured for admin functions, or if the SQL injection is reachable without credentials
-
Assess database user privilegesExamine the database user credentials configured in your SLiMS config file (usually config.php or database configuration) to determine if the application database user has elevated privilegesAffected if The database user has privileges beyond SELECT (such as INSERT, UPDATE, DELETE, or administrative rights)
Your environment is affected if you are running SLiMS 9.6.1 or earlier, the coll_type.php file exists in your installation, and the admin module is network-accessible to untrusted users.
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 dataUpgrade to a patched version of SLiMS (if available) or implement input validation and parameterized queries (prepared statements) for all database interactions in coll_type.php and similar admin files to prevent SQL injection attacks.
- 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-25403 — 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-25403 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