CVE-2023-40750
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 · uneditedThere is a Cross Site Scripting (XSS) vulnerability in the "action" parameter of index.php in PHPJabbers Yacht Listing Script v1.0.
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 confidenceA Cross Site Scripting (XSS) vulnerability exists in the 'action' parameter of index.php in PHPJabbers Yacht Listing Script v1.0. Attackers can inject malicious JavaScript or HTML code through the unsanitized action parameter, which gets reflected in the web page response without proper output encoding.
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.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 PHPJabbers Yacht Listing Script installationLocate the web application's directory structure and confirm the presence of index.php in the document root. Look for files or folders indicating this specific product (such as 'yacht-listing' directory or references to PHPJabbers Yacht Listing Script).Affected if The application directory contains index.php and is identified as the PHPJabbers Yacht Listing Script software.
-
Verify the installed version is 1.0Check for a version file, README, or changelog in the application root. Alternatively, view the source code of index.php for a version comment or constant defining the version number.Affected if The version is confirmed to be exactly 1.0.
-
Examine the action parameter handling in index.phpOpen index.php and locate the code that handles the 'action' parameter (typically via $_GET['action'] or $_REQUEST['action']). Inspect how this value is used in the response without output encoding.Affected if The 'action' parameter value is directly echoed or printed in the HTML response without using functions like htmlspecialchars(), htmlentities(), or equivalent encoding.
-
Test for XSS reflectionSend a request to index.php with a crafted 'action' parameter containing JavaScript payload, for example: index.php?action=<script>alert('XSS')</script>. Inspect the response to see if the script tags are reflected as-is in the HTML output.Affected if The injected script tags appear unmodified in the page source, indicating lack of output encoding and confirming the XSS vulnerability.
The environment is affected if PHPJabbers Yacht Listing Script version 1.0 is installed and the 'action' parameter in index.php is reflected in the HTTP response without sanitization or output encoding.
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 action parameter in index.php to neutralize malicious script injection. The fix involves sanitizing user-supplied input before reflecting it in the HTTP response.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-40750 — 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-2023-40750 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