CVE-2024-33980
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 · uneditedCross-Site Scripting (XSS) vulnerability in PayPal, Credit Card and Debit Card Payment 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 'start' parameter in '/admin/mod_reports/printreport.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 · moderate confidenceReflected XSS vulnerability in the 'start' parameter of /admin/mod_reports/printreport.php in PayPal, Credit Card and Debit Card Payment version 1.0. An attacker can craft a malicious URL that executes JavaScript in the victim's browser to exfiltrate session cookies.
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.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
- 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 checksWork through these to decide whether this CVE applies to you.
-
Confirm application installation and identify versionLocate the application files on the web server. Check for version.php, readme.txt, or any version identifier within the application root directory. If using a package manager or CMS, check the installed package version.Affected if The installed version matches 1.0 of Janobe Credit Card, Janobe Debit Card Payment, or Janobe PayPal.
-
Verify vulnerable endpoint is accessibleAttempt to access the path /admin/mod_reports/printreport.php through the web browser or curl command. Confirm the page loads and accepts parameters.Affected if The endpoint /admin/mod_reports/printreport.php is reachable and returns a valid HTTP response.
-
Test the start parameter for XSS vulnerabilitySend a crafted request to the vulnerable endpoint with a benign XSS test payload in the 'start' parameter, such as: /admin/mod_reports/printreport.php?start=<script>alert(1)</script>. Inspect the response to see if the payload is reflected without proper encoding.Affected if The 'start' parameter value is reflected in the response HTML without sanitization or encoding, indicating the XSS vulnerability is present.
-
Check session cookie security configurationLog into the application and examine the session cookie set by the application. Use browser developer tools or curl -v to inspect the Set-Cookie header. Verify if HttpOnly and Secure flags are present.Affected if Session cookies are set without the HttpOnly flag, allowing JavaScript access to cookies, or without the Secure flag on HTTPS deployments.
A user is affected if they run version 1.0 of any Janobe payment product, the vulnerable printreport.php endpoint is accessible, and the 'start' parameter reflects unsanitized input or lacks HttpOnly cookie protection.
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 dataImplement input validation and output encoding for the 'start' parameter in printreport.php, and configure session cookies with HttpOnly and Secure flags to prevent cookie theft via XSS.
- Consultation2.0 h
- Implementation3.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,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-33980 — 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-33980 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