CVE-2024-33964
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 'id' in '/admin/mod_users/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 confidenceSQL injection vulnerability in the 'id' parameter of /admin/mod_users/index.php in PayPal, Credit Card and Debit Card Payment version 1.0. An attacker can send specially crafted SQL queries via 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 if Janobe software is installedLook for PHP application files on the web server, typically in the web root directory. Common installation paths may include /var/www/html/, /www/, or the document root. Search for files named index.php, particularly in admin/ directories.Affected if Janobe Credit Card, Debit Card Payment, PayPal, School Attendance Monitoring System, or School Event Management System PHP files are present on the server
-
Check the installed versionExamine the application for version information. Check README files, config files, or the main index.php for a version number. The affected version is specifically 1.0.Affected if The installed version is exactly 1.0
-
Verify the vulnerable file existsLocate and verify the presence of the file /admin/mod_users/index.php in the web application directory structure.Affected if The file /admin/mod_users/index.php exists in the application
-
Confirm admin access is possibleCheck if the /admin/ directory is accessible via the web server without authentication restrictions, or if default admin credentials are in use.Affected if The admin interface at /admin/ is accessible, enabling interaction with the vulnerable parameter
-
Check for SQL injection vulnerability in the id parameterReview the source code of /admin/mod_users/index.php to determine if the 'id' parameter is used directly in SQL queries without proper sanitization, prepared statements, or parameter binding.Affected if The 'id' parameter from GET or POST requests is concatenated directly into SQL queries without escaping or parameterization
A user is affected if they have Janobe software version 1.0 installed with the vulnerable /admin/mod_users/index.php file accessible and the 'id' parameter implemented without parameterized queries.
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 statements (prepared statements) or implement proper input validation and escaping for the 'id' parameter before using it in database queries.
- Consultation3.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,304.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-33964 — 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-33964 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