dbcve.org
Credit CardApplication · Janobe

CVE-2024-33968

HIGH · 7.5 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 →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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
SQL injection vulnerability in PayPal, Credit Card and Debit Card Payment affecting version 1.0. An attacker could exploit this vulnerability by sending a specially crafted query to the server and retrieve all the information stored in it through the following 'Attendance' and 'YearLevel' in '/AttendanceMonitoring/report/index.php' parameter.

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

Unauthenticated SQL injection vulnerability in the AttendanceMonitoring report endpoint (/AttendanceMonitoring/report/index.php) where the 'Attendance' and 'YearLevel' parameters are not properly sanitized, allowing attackers to inject malicious SQL queries and extract sensitive data from the database.

MitigationImplement prepared statements/parameterized queries for all SQL queries in the affected report functionality, and apply proper input validation on the Attendance and YearLevel parameters.

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
Credit CardApplication
Affected:= 1.0
Debit Card PaymentApplication
Affected:= 1.0
PaypalApplication
Affected:= 1.0
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
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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 the installed Janobe product
    Locate and inspect the application to determine which Janobe product is deployed (Credit Card, Debit Card Payment, Paypal, School Attendance Monitoring System, or School Event Management System). Check the application name, title, or documentation files for product identification.
    Affected if Any of the five Janobe products (Credit Card, Debit Card Payment, Paypal, School Attendance Monitoring System, or School Event Management System) is installed.
  2. Verify the application version is 1.0
    Check the application version by inspecting version files, footer text, about pages, or configuration files. Compare the installed version against the affected range (= 1.0).
    Affected if The installed version equals 1.0.
  3. Confirm the AttendanceMonitoring module exists
    Inspect the web root directory for the presence of the /AttendanceMonitoring/report/ folder and the index.php file. Check if the path /AttendanceMonitoring/report/index.php is accessible on the server.
    Affected if The AttendanceMonitoring/report/index.php file exists and is accessible via web request.
  4. Test the vulnerable parameters
    Send a benign HTTP GET or POST request to /AttendanceMonitoring/report/index.php with test values in the 'Attendance' and 'YearLevel' parameters. Observe if the application processes the input without proper escaping or error handling.
    Affected if The application accepts input in the Attendance and YearLevel parameters without rejecting or escaping SQL special characters.

If a Janobe product version 1.0 is running and the AttendanceMonitoring/report/index.php endpoint is accessible with the Attendance and YearLevel parameters, the environment is affected by this SQL injection vulnerability.

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 prepared statements/parameterized queries for all SQL queries in the affected report functionality, and apply proper input validation on the Attendance and YearLevel parameters.

Fix this in Credit Card Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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