CVE-2023-36313
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 Document Creator v1.0 is vulnerable to Cross Site Scripting (XSS) via all post parameters of "Export Requests" aside from "request_feed".
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 confidencePHPJabbers Document Creator v1.0 contains a reflected Cross Site Scripting (XSS) vulnerability in the 'Export Requests' functionality. Multiple POST parameters (excluding 'request_feed') fail to properly sanitize user input, allowing attackers to inject malicious JavaScript code that executes in the context of victim's browser.
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 the installed product and versionLocate and inspect the PHPJabbers Document Creator installation. Check version files, about pages, or admin panels to confirm the exact version number. Compare it to the affected range: version 1.0 specifically.Affected if The product is PHPJabbers Document Creator version 1.0 exactly.
-
Locate the Export Requests functionalityNavigate through the application interface or examine the source code to find the 'Export Requests' feature. This is typically accessible via the admin panel or a dedicated menu item.Affected if The Export Requests feature exists and is accessible in the application.
-
Identify POST parameters in the Export Requests formExamine the Export Requests form submission by reviewing the HTML source code or using a browser developer tool to inspect form elements. Identify all POST parameters submitted by the form.Affected if The form accepts multiple POST parameters (other than just 'request_feed') for processing.
-
Verify lack of input sanitizationTest the Export Requests functionality by submitting form data with special characters (such as <script>alert(1)</script> or javascript:alert(1)) in the POST parameters and observe if these characters are reflected back in the response without encoding.Affected if User-supplied input in POST parameters is reflected in the response without proper HTML encoding or sanitization.
A user is affected if they are running PHPJabbers Document Creator version 1.0 and the Export Requests functionality reflects unsanitized POST parameter input in the response.
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 all POST parameters in the Export Requests functionality. Use context-appropriate escaping and consider implementing a Content Security Policy (CSP) as defense-in-depth.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.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 $2,848.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-36313 — 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-36313 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