CVE-2024-28276
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 · uneditedSourcecodester School Task Manager 1.0 is vulnerable to Cross Site Scripting (XSS) via add-task.php?task_name=.
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 confidenceThis is a reflected Cross-Site Scripting (XSS) vulnerability in Sourcecodester School Task Manager 1.0. The vulnerability exists in the add-task.php file where the task_name parameter is not properly sanitized or validated before being reflected back in the HTML output, allowing an attacker to inject malicious JavaScript code.
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
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/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 application and identify its versionSearch the web root directory for version indicators such as readme.txt, version.php, or any file containing '1.0' or 'School Task Manager'. Check the application's header/footer files for version strings.Affected if The application installed is Rems School Task Manager version 1.0 exactly.
-
Verify the vulnerable file existsCheck if the file add-task.php exists in the web-accessible directories, typically under the main application path (e.g., /add-task.php or /includes/add-task.php).Affected if The add-task.php file is present in the deployed application.
-
Confirm the application is accessible and operationalAttempt to access the application's main page and verify the add-task.php endpoint responds to HTTP requests. Use a browser or curl to request the page.Affected if The application is running and the add-task.php page is reachable via HTTP.
-
Identify the task_name parameter handlingReview the add-task.php source code to confirm the task_name parameter is reflected in the HTML response without sanitization. Look for echo, print, or print_r statements outputting $_POST['task_name'] or $_GET['task_name'] directly.Affected if The code shows task_name is output directly into HTML without encoding, escaping, or validation functions.
You are affected if you are running Rems School Task Manager version 1.0 with the add-task.php file accessible and the task_name parameter being reflected without proper sanitization in the HTML output.
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 proper input validation and output encoding/escaping for the task_name parameter in add-task.php. All user-supplied data should be validated against an allowlist and any output rendered in HTML context must be properly escaped.
- Consultation1.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-28276 — 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-28276 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