CVE-2025-13240
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 vulnerability was detected in code-projects Student Information System 2.0. This affects an unknown part of the file /searchquery.php. Performing manipulation of the argument s results in sql injection. Remote exploitation of the attack is possible. The exploit is now public and may be used.
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 code-projects Student Information System 2.0 allows remote attackers to manipulate the 's' parameter in /searchquery.php to inject arbitrary SQL queries. The lack of input sanitization or parameterized queries enables attackers to access, modify, or delete database contents. Public exploit availability increases urgency.
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= 2.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 the application installationSearch the web server filesystem for the 'searchquery.php' file, typically found in the web root directory under a path like /var/www/html/ or C:\inetpub\wwwroot\Affected if The file /searchquery.php exists and belongs to Fabian Student Information System version 2.0
-
Verify the product versionCheck for a version file (version.txt, README, or within index.php) or examine the application source code for a version identifier matching 2.0Affected if The installed version is exactly 2.0 ( Fabian Student Information System)
-
Examine the vulnerable code in searchquery.phpOpen /searchquery.php in a text editor and search for SQL query construction involving the 's' parameter - look for unsanitized variable usage in SELECT statementsAffected if The 's' parameter is directly concatenated into SQL queries without prepared statements, parameterized queries, or input sanitization
-
Confirm the search endpoint is accessibleAttempt an HTTP GET request to the /searchquery.php endpoint (e.g., curl or browser access to http://TARGET/searchquery.php)Affected if The endpoint responds and accepts the 's' parameter without authentication or CSRF protection
-
Check for other SQL injection pointsSearch the codebase for other PHP files containing SQL queries that use $_GET, $_POST, or $_REQUEST variables without sanitization or prepared statementsAffected if Additional files contain similar SQL injection patterns using unsanitized user input
A user is affected if Fabian Student Information System version 2.0 is installed and the /searchquery.php file contains unsanitized 's' parameter usage in SQL 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 dataReplace dynamic SQL queries with parameterized queries or prepared statements in /searchquery.php, apply input validation and escaping for the 's' parameter, and conduct a broader code review to identify similar SQL injection vulnerabilities throughout the application.
- 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-13240 — 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-13240 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