dbcve.org
Credit CardApplication · Janobe

CVE-2024-33979

MEDIUM · 6.1 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 →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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
Cross-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 'q', 'arrival', 'departure' and 'accomodation' parameters in '/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 · high confidence

A reflected Cross-Site Scripting (XSS) vulnerability exists in the PayPal, Credit Card and Debit Card Payment WordPress plugin version 1.0. The vulnerability affects the '/index.php' file via the 'q', 'arrival', 'departure', and 'accommodation' parameters. An attacker can craft a malicious URL containing JavaScript that, when clicked by a victim, executes in their browser to steal session cookies.

MitigationImplement proper input validation and output encoding for all user-suprollable parameters ('q', 'arrival', 'departure', 'accommodation') in '/index.php'. Use built-in WordPress sanitization functions like esc_html() and esc_attr() for output, and consider adding Content-Security-Policy headers to provide defense-in-depth.

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

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
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 checks

Work through these to decide whether this CVE applies to you.

  1. Verify the Janobe plugin is installed
    Navigate to WordPress Admin Dashboard > Plugins. Look for 'Janobe Credit Card', 'Janobe Debit Card Payment', or 'Janobe Paypal' in the installed plugins list.
    Affected if Any of these three plugins appear in the installed plugins list at version 1.0
  2. Confirm the plugin version
    In the Plugins list, click on the plugin and look for the version number displayed in the plugin details. Alternatively, check the plugin header in the main PHP file (typically in wp-content/plugins/ folder under the plugin directory name).
    Affected if The installed version is exactly 1.0 (the affected version)
  3. Locate the vulnerable index.php file
    Access the site via FTP or file manager and locate the plugin directory. The vulnerable file is /index.php within the plugin folder. Common path: wp-content/plugins/[plugin-name]/index.php
    Affected if The file /index.php exists in the plugin directory
  4. Inspect the vulnerable parameter handling
    Open the index.php file and search for usage of the parameters 'q', 'arrival', 'departure', or 'accommodation'. Check if these parameters are echoed back to the user without proper sanitization (look for absence of esc_html(), esc_attr(), or similar WordPress escaping functions).
    Affected if Any of these four parameters are processed and output without escaping functions like esc_html() or esc_attr()
  5. Test for XSS vulnerability (safe probe only)
    On a non-production/test site, visit a URL like: yoursite.com/index.php?q=<script>alert('test')</script> and check if the script tag appears literally in the page source or executes.
    Affected if The parameter value is reflected unescaped in the HTML output

You are affected if the Janobe Credit Card, Debit Card, or PayPal plugin version 1.0 is installed and the index.php file handles any of the q, arrival, departure, or accommodation parameters without output encoding.

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 proper input validation and output encoding for all user-suprollable parameters ('q', 'arrival', 'departure', 'accommodation') in '/index.php'. Use built-in WordPress sanitization functions like esc_html() and esc_attr() for output, and consider adding Content-Security-Policy headers to provide defense-in-depth.

Fix this in Credit Card Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,690
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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