CVE-2025-14950
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 · uneditedA weakness has been identified in code-projects Scholars Tracking System 1.0. The affected element is an unknown function of the file /delete_post.php. This manipulation of the argument ID causes sql injection. Remote exploitation of the attack is possible. The exploit has been made available to the public and could be used for attacks.
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 Scholars Tracking System 1.0's /delete_post.php file allows remote attackers to inject malicious SQL queries via the ID parameter. The lack of input sanitization or parameterized queries in the delete function enables complete database compromise.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 1.0CVSS 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.
-
Locate Scholars Tracking System installationSearch the web server document root for the 'delete_post.php' file. Common paths include /var/www/html/, /www/, or C:\inetpub\wwwroot\. Look for directories containing 'scholars' or 'fabian' in the name.Affected if The delete_post.php file exists in the web application's directory structure.
-
Verify application versionCheck for a version file in the application root (such as version.php, readme.txt, or about.php). Review any documentation or meta files for version number '1.0'.Affected if The installed version is Fabian Scholars Tracking System 1.0.
-
Inspect delete_post.php for SQL injection flawOpen delete_post.php in a text editor. Search for SQL query patterns that directly use the ID parameter without prepared statements, parameterized queries, or input sanitization. Look for patterns like $id = $_GET['id']; followed by a raw SQL query containing $id.Affected if The code contains unsanitized dynamic SQL queries using the ID parameter.
-
Confirm parameter handling is vulnerableExamine how the ID parameter is processed. Check if the code uses mysqli_prepare, PDO::prepare, or any escaping functions (mysqli_real_escape_string, htmlspecialchars) before building SQL queries.Affected if The ID parameter is directly concatenated into SQL queries without prepared statements or escaping functions.
If the system runs Fabian Scholars Tracking System 1.0 with the delete_post.php file containing direct SQL query construction using the unsanitized ID parameter, the environment is affected by this SQL injection vulnerability.
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 dataReplace dynamic SQL queries with prepared statements/parameterized queries in delete_post.php, implement input validation on the ID parameter, and apply principle of least privilege to the database user.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-14950 — 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-14950 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