dbcve.org
Yacht Listing ScriptApplication · Phpjabbers

CVE-2023-38830

HIGH · 7.5 CVSS v3.1 Published 2023-08-10
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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
An information leak in PHPJabbers Yacht Listing Script v1.0 allows attackers to export clients' credit card numbers from the Reservations module.

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 confidence

An information disclosure vulnerability in PHPJabbers Yacht Listing Script v1.0 allows attackers to export clients' credit card numbers from the Reservations module, likely due to insufficient access controls or improper handling of sensitive payment data.

MitigationRestrict access to the Reservations export functionality and implement proper encryption, tokenization, or masking of credit card data following PCI-DSS compliance requirements.

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
Yacht Listing ScriptApplication
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
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 checks

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

  1. Verify PHPJabbers Yacht Listing Script version
    Locate the script installation directory and check the version identifier in the software documentation, admin panel, or version file. This is typically found in a config file, README, or the admin dashboard under 'System' or 'About' sections.
    Affected if The installed version is exactly 1.0
  2. Confirm Reservations module is active
    Log into the admin panel and navigate to the module management section. Check whether the Reservations module is enabled and accessible. This is usually found under 'Modules' or 'Features' in the admin dashboard.
    Affected if The Reservations module is installed and enabled in the system
  3. Identify export functionality in Reservations
    Access the Reservations section in the admin panel and locate any export, download, or data extraction features. Look for buttons or links labeled 'Export', 'Download', 'CSV', 'PDF', or similar that allow downloading reservation data.
    Affected if Export functionality exists and is accessible within the Reservations module
  4. Review export output for sensitive data exposure
    Use the Reservations export feature to generate a sample export file. Open the file and inspect the fields included in the output. Check whether any fields contain full or partial credit card numbers, CVV codes, or other payment card data.
    Affected if The exported data includes credit card numbers or other PCI-DSS protected payment card data in plaintext or unmasked form
  5. Check access control on Reservations export
    Test accessing the Reservations export functionality from different user roles (admin, staff, limited user) without authentication, or verify if the export feature requires authentication and proper authorization before allowing data download.
    Affected if The export feature can be accessed by unauthorized users or users without proper role-based access to payment data

A user is affected if the PHPJabbers Yacht Listing Script version is exactly 1.0, the Reservations module is enabled, and the export functionality exposes credit card numbers in its output without proper access controls.

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

Restrict access to the Reservations export functionality and implement proper encryption, tokenization, or masking of credit card data following PCI-DSS compliance requirements.

Fix this in Yacht Listing Script Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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