CVE-2024-26517
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 · uneditedSQL Injection vulnerability in School Task Manager v.1.0 allows a remote attacker to obtain sensitive information via a crafted payload to the delete-task.php component.
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 School Task Manager v1.0's delete-task.php allows remote attackers to inject malicious SQL queries via unsanitized user input, enabling extraction of sensitive data from the database.
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
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
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 School Task Manager installationSearch for the 'delete-task.php' file in your web server's document root or application directory. Common paths may include /school-task-manager/, /task-manager/, or similar subdirectories.Affected if The file 'delete-task.php' exists in your web-accessible directories and the application is running version 1.0
-
Confirm the application versionCheck the application's source code for a version identifier. Look in files like version.php, about.php, or the main index.php for a version string. Alternatively, check the application's admin panel or README file for version information.Affected if The installed version is exactly 1.0 (Rems School Task Manager)
-
Verify delete-task.php is accessibleAttempt to access delete-task.php directly via HTTP/HTTPS request to confirm it is reachable. For example: GET /delete-task.php or /path/to/delete-task.phpAffected if The file responds to HTTP requests and processes parameters without immediate error
-
Inspect the delete-task.php source codeOpen delete-task.php in a text editor and examine how it handles user input, particularly looking for direct inclusion of $_GET, $_POST, or $_REQUEST parameters in SQL queries without using prepared statements or escaping functions.Affected if The code contains SQL queries that directly concatenate user input (e.g., $_REQUEST['id'], $_GET['task_id']) into the query string without parameter binding or input sanitization
You are affected if you are running School Task Manager version 1.0 with delete-task.php accessible and that file contains unsanitized user input in SQL query constructs.
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 database interactions in delete-task.php and apply proper input validation to prevent SQL injection attacks.
- Consultation3.0 h
- Implementation4.0 h
- Testing2.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,168.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-26517 — 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-2024-26517 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