CVE-2023-36314
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 value-text-o_sms_email_request_message parameters of index.php in PHPJabbers Callback Widget 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 · high confidenceA reflected Cross Site Scripting (XSS) vulnerability exists in PHPJabbers Callback Widget v1.0 within the index.php file. The vulnerability affects the value-text-o_sms_email_request_message parameter, allowing attackers to inject malicious JavaScript code that executes in the context of a user's browser when they interact with the affected input field.
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 Callback Widget installationCheck your web server's document root for a folder named 'callback-widget' or similar, and look for an index.php file. Verify the application name in the source code comments or configuration files.Affected if The PHPJabbers Callback Widget v1.0 is present on the server
-
Locate the vulnerable index.php fileNavigate to the callback widget directory and identify the index.php file. Open it in a text editor or use 'grep' to search for the string 'o_sms_email_request_message' within the file.Affected if The index.php file exists and contains the o_sms_email_request_message parameter handling code
-
Inspect the parameter handling logicSearch the index.php file for code that handles the 'o_sms_email_request_message' or similar SMS/email request message parameter. Look for sections where user input is assigned to variables without proper sanitization.Affected if The parameter is processed and displayed without htmlspecialchars() or equivalent encoding
-
Check if the application outputs user input unsafelyReview the code around the o_sms_email_request_message parameter. Look for echo or print statements that output this parameter value directly into HTML without escaping functions.Affected if The code outputs the message parameter directly into HTML without encoding
-
Test the reflected XSS in a safe test environmentIf you have a staging environment, submit a benign test payload such as '<script>alert(1)</script>' in the message field and observe if the script executes when the page reloads or displays the submitted value.Affected if The test payload executes as JavaScript in the browser, confirming the XSS is exploitable
You are affected if PHPJabbers Callback Widget v1.0 is installed and the index.php file processes the o_sms_email_request_message parameter without proper 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 o_sms_email_request_message parameter. Use context-appropriate escaping functions (such as htmlspecialchars() in PHP) before rendering user-supplied data in HTML output.
- 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-36314 — 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-36314 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