CVE-2024-33989
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 · uneditedCross-Site Scripting (XSS) vulnerability in School Event Management System affecting version 1.0. An attacker could exploit this vulnerability by sending a specially crafted javascript payload to an authenticated user and partially take over their browser session via the 'eventdate' and 'events' parameters in 'port/event_print.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 confidenceStored Cross-Site Scripting (XSS) vulnerability in School Event Management System v1.0. Authenticated attackers can inject malicious JavaScript payloads through the 'eventdate' and 'events' parameters in port/event_print.php, allowing partial browser session hijacking of other users who view the injected content.
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.
-
Confirm School Event Management System installationLocate the application installation directory and check for version indicators such as version files, README files, or the admin dashboard version display. Common paths include /var/www/html/ or C:\xampp\htdocs\ on web servers.Affected if The installed version is exactly 1.0 of Janobe School Event Management System
-
Verify vulnerable file existsCheck if the file port/event_print.php exists in the web application root directory. Use file system search or check via HTTP request to the path.Affected if The file port/event_print.php exists and is accessible via the web server
-
Check for authenticated access to event managementDetermine if user authentication is available and functional in the system. Check if there are user accounts that can access event creation or editing functions.Affected if Authenticated users can access the event creation or editing functionality that populates the eventdate and events parameters
-
Inspect event storage for malicious payloadsExamine the database or application storage where event data is saved. Query the events table for any suspicious script tags, javascript: URIs, or event handler attributes in eventdate or events fields.Affected if Stored XSS payloads (script tags, event handlers) are present in the eventdate or events database fields
-
Verify vulnerable parameter handling in event_print.phpAccess port/event_print.php with a test event ID and inspect the HTML source to confirm if eventdate and events parameters are rendered without proper encoding.Affected if The eventdate and events values are rendered in HTML output without sanitization or encoding
You are affected if you are running School Event Management System version 1.0 and the port/event_print.php file is accessible with unencoded eventdate or events parameters in the 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 input validation and output encoding/sanitization for the 'eventdate' and 'events' parameters in port/event_print.php before rendering user-supplied data in HTML contexts.
- Consultation3.0 h
- Implementation4.0 h
- Testing3.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,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-33989 — 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-33989 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