CVE-2024-33981
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/index.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/index.php in the PayPal, Credit Card and Debit Card Payment plugin version 1.0 allows attackers to inject malicious JavaScript via a crafted URL to steal victim 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.
-
Identify Janobe plugin installationLocate and check the version of the installed Janobe plugin (Credit Card, Debit Card, or PayPal). Look for version files or check plugin metadata in the installation directory.Affected if The installed plugin version is exactly 1.0 for any of these three: Janobe Credit Card, Janobe Debit Card Payment, or Janobe Paypal.
-
Verify vulnerable file existsCheck for the presence of /admin/mod_reports/index.php in the web application root directory.Affected if The file /admin/mod_reports/index.php exists in the application.
-
Inspect parameter handling codeOpen /admin/mod_reports/index.php and examine how the 'start' parameter is processed. Look for the use of $_GET['start'] or $_REQUEST['start'] without sanitization functions such as htmlspecialchars(), htmlentities(), or input validation.Affected if The 'start' parameter is retrieved and used in output (e.g., echoed back) without being sanitized through encoding functions.
-
Test for XSS in live environmentSend a crafted request with a benign XSS payload in the start parameter, for example: /admin/mod_reports/index.php?start=<script>alert(1)</script> and verify whether the payload is reflected unescaped in the response.Affected if The payload is reflected directly in the HTML response without being escaped or encoded.
You are affected if you are running any of the Janobe Credit Card, Debit Card Payment, or Janobe Paypal plugins at version 1.0 and the /admin/mod_reports/index.php file is present with unescaped output of the 'start' parameter.
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 strict input validation and output encoding on the 'start' parameter; deploy SameSite cookies and HttpOnly flags as defense-in-depth.
- Consultation1.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 $1,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-33981 — 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-33981 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