dbcve.org
School Attendence Monitoring SystemApplication · Janobe

CVE-2024-33988

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' and 'YearLevel' parameters in '/report/attendance_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 · high confidence

A reflected Cross-Site Scripting (XSS) vulnerability exists in the attendance_print.php script of the School Attendance Monitoring System v1.0. The 'Attendance', 'attenddate', and 'YearLevel' parameters accept user input without proper sanitization, allowing attackers to inject malicious JavaScript via crafted URLs to exfiltrate victim session cookies.

MitigationImplement input validation and output encoding for all user-supplied parameters in attendance_print.php. Use context-appropriate escaping (e.g., htmlspecialchars in PHP) before reflecting any user input back in HTML output.

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. Identify installed School Attendance Monitoring System
    Locate the web application files and determine if the Janobe School Attendance Monitoring System or School Event Management System v1.0 is present on the server. Check for the presence of attendance_print.php in the web root or application directory.
    Affected if The application directory contains attendance_print.php and the system is Janobe School Attendance Monitoring System or Event Management System version 1.0
  2. Locate the vulnerable script
    Search the file system for the file named attendance_print.php. Verify its full path within the web application structure.
    Affected if The file attendance_print.php exists in the web application directory
  3. Inspect parameter handling in attendance_print.php
    Open attendance_print.php and examine how the 'Attendance', 'attenddate', and 'YearLevel' parameters are handled. Look for whether these parameters are directly echoed or reflected in the HTML output without sanitization functions such as htmlspecialchars.
    Affected if The code shows these parameters being output directly without sanitization (e.g., no htmlspecialchars, no input validation)
  4. Verify script is accessible via web
    Confirm the attendance_print.php script is accessible over HTTP/HTTPS. Attempt to access it with a test query string containing the vulnerable parameters.
    Affected if The script responds to HTTP requests and processes the 'Attendance', 'attenddate', or 'YearLevel' parameters from the query string

The environment is affected if the Janobe School Attendance Monitoring System or Event Management System v1.0 is installed, the attendance_print.php file exists, and the code reflects user input from the 'Attendance', 'attenddate', or 'YearLevel' parameters without sanitization.

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 attendance_print.php. Use context-appropriate escaping (e.g., htmlspecialchars in PHP) before reflecting any user input back in HTML output.

Fix this in School Attendence Monitoring System Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
Get help mitigating

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-33988 — 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-33988 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