dbcve.org
School Attendence Monitoring SystemApplication · Janobe

CVE-2024-33987

MEDIUM · 6.1 CVSS v3.1 Published 2024-08-06
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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 · unedited
Cross-Site Scripting (XSS) vulnerability in School Attendance Monitoring System and School Event Management System affecting version 1.0. An attacker could create a specially crafted URL and send it to a victim to obtain details of their session cookie via the 'Attendance', 'attenddate', 'YearLevel', 'eventdate', 'events', 'Users' and 'YearLevel' parameters in '/report/index.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 · high confidence

Reflected XSS vulnerability in School Attendance Monitoring System and School Event Management System v1.0 allows attackers to inject malicious JavaScript via multiple parameters (Attendance, attenddate, YearLevel, eventdate, events, Users) in /report/index.php. When victims click crafted URLs, the injected script executes in their browsers, enabling session cookie theft and session hijacking.

MitigationImplement input validation and output encoding for all user-supplied parameters in /report/index.php. Additionally, configure session cookies with HttpOnly and Secure flags to prevent XSS-based cookie theft.

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
School Attendence Monitoring SystemApplication
Affected:= 1.0
School Event Management SystemApplication
Affected:= 1.0

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm the affected application is installed
    Locate the School Attendance Monitoring System or School Event Management System installation directory. Identify if the file /report/index.php exists within the web root.
    Affected if The file /report/index.php is present in the web application directory.
  2. Verify the installed version is 1.0
    Check the application's version information (typically found in an about page, version file, or software documentation within the installation directory). Compare your installed version to the affected range.
    Affected if The installed version is exactly 1.0 for either system.
  3. Inspect the vulnerable parameters in /report/index.php
    Examine the source code of /report/index.php and locate the handling of parameters: Attendance, attenddate, YearLevel, eventdate, events, and Users. Determine if these parameters are directly echoed to output without sanitization or encoding.
    Affected if Any of these parameters are output to the page without proper HTML encoding or input validation.
  4. Test for reflected XSS execution
    Craft a test URL using one of the vulnerable parameters (e.g., /report/index.php?Attendance=<script>alert(1)</script>) and request it in a browser or using a tool like curl. Observe if the script tag is reflected unencoded in the response.
    Affected if The injected script tag appears verbatim in the HTTP response without being HTML-encoded.
  5. Check session cookie security configuration
    Inspect the session cookie configuration in the application or server settings. Look for the HttpOnly and Secure flags being set on session cookies.
    Affected if Session cookies lack the HttpOnly flag, making them accessible to JavaScript and vulnerable to theft via XSS.

You are affected if the application version is 1.0, /report/index.php exists, and any of the specified parameters reflect user input without HTML encoding in the response.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement input validation and output encoding for all user-supplied parameters in /report/index.php. Additionally, configure session cookies with HttpOnly and Secure flags to prevent XSS-based cookie theft.

Fix this in School Attendence Monitoring System Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-33987 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-33987 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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