CVE-2024-33962
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 · uneditedSQL 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 'code' in '/admin/mod_reservation/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 confidenceA SQL injection vulnerability exists in the 'code' parameter of /admin/mod_reservation/index.php in version 1.0 of a PayPal, Credit Card and Debit Card Payment system. An unauthenticated or authenticated attacker can inject malicious SQL queries through this parameter to exfiltrate sensitive data from the database.
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.0= 1.0= 1.0= 1.0= 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
- 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 checksWork through these to decide whether this CVE applies to you.
-
Identify the installed Janobe product and versionCheck your web application's about page, footer, or source code for the product name and version number. Common locations include the login page, header/footer files, or a /about page.Affected if The installed product is one of: Janobe Credit Card, Janobe Debit Card Payment, Janobe PayPal, Janobe School Attendance Monitoring System, or Janobe School Event Management System at version 1.0
-
Verify the vulnerable file existsLocate the web root directory and check for the existence of /admin/mod_reservation/index.php. The path may vary based on your installation directory structure.Affected if The file /admin/mod_reservation/index.php exists in the web application
-
Check if the reservation module is accessibleAttempt to access the reservation module through the web interface or check if the mod_reservation directory is exposed via web server. Look for any URLs containing /admin/mod_reservation/ or similar paths.Affected if The reservation module is accessible without proper access controls or is publicly reachable
-
Test for SQL injection on the code parameterIf the reservation page is accessible, inspect the 'code' parameter in the URL or form submissions. Test by submitting a benign payload such as 'code=123' and observe the response. A vulnerable application may reflect input or return database errors.Affected if The application reflects the 'code' parameter input without sanitization or returns SQL error messages
-
Verify admin panel accessibilityCheck whether the /admin/ directory or admin panel is accessible without authentication by attempting to access it directly from an unauthenticated browser or using a web scanner.Affected if The admin panel or reservation module can be accessed without authentication
You are affected if you are running any of the listed Janobe products at version 1.0 and the /admin/mod_reservation/index.php file exists with the reservation module accessible, as the SQL injection in the code parameter can be exploited.
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 dataReplace dynamic SQL queries with parameterized queries/prepared statements and implement proper input validation on the 'code' parameter. Restrict access to the admin panel to authorized users only.
- 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-33962 — 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-33962 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