CVE-2023-40751
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 · uneditedPHPJabbers Fundraising Script v1.0 is vulnerable to Cross Site Scripting (XSS) via the "action" parameter of 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 confidencePHPJabbers Fundraising Script v1.0 contains a reflected Cross Site Scripting (XSS) vulnerability in the 'action' parameter of index.php. An unauthenticated attacker could inject malicious JavaScript code into the URL parameter that would execute in the victim's browser when the crafted link is visited.
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.
-
Confirm PHPJabbers Fundraising Script installationSearch for the 'index.php' file in your web root directory and verify it belongs to the PHPJabbers Fundraising Script product by checking for branding text or file headers that identify it as this specific product.Affected if The script is installed and accessible on your server.
-
Identify the installed versionExamine the source code of index.php for a version identifier, or check for a version file or database configuration that indicates the product version. Compare against version 1.0.Affected if The installed version is exactly 1.0.
-
Locate the 'action' parameter handlingSearch the index.php source code for occurrences of 'action' as a request parameter (e.g., $_GET['action'], $_REQUEST['action']) and identify where this value is output or reflected back to the user.Affected if The 'action' parameter is processed and reflected in the page output.
-
Check for output encoding on the 'action' parameterExamine the code where the 'action' parameter is reflected to see if it is wrapped in htmlspecialchars() or equivalent encoding functions before output. Look for patterns like echo $_GET['action'] without encoding.Affected if The 'action' parameter is reflected without proper HTML encoding (no htmlspecialchars or equivalent).
-
Verify the vulnerable code path is reachableAttempt to access the index.php with a test query string such as '?action=test' and examine the response to confirm the value is reflected in the HTML output without sanitization.Affected if The 'action' parameter value appears verbatim in the rendered HTML page.
Your environment is affected if you are running PHPJabbers Fundraising Script version 1.0 and the 'action' parameter from index.php is reflected in the page output without HTML 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 proper input validation and output encoding for the 'action' parameter. Use htmlspecialchars() or equivalent encoding functions in PHP to sanitize user-supplied input before reflecting it in the HTML response.
- Consultation2.0 h
- Implementation2.0 h
- Testing1.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,744.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-40751 — 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-40751 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