CVE-2023-37225
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 · uneditedPexip Infinity before 32 allows Webapp1 XSS via preconfigured links.
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 confidenceCross-site scripting (XSS) vulnerability in Pexip Infinity conferencing platform affecting the Webapp1 component via preconfigured links. Attackers can inject malicious scripts through specially crafted links that are then executed in the context of the victim's browser session.
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< 32.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 Pexip Infinity is deployedLocate Pexip Infinity by accessing the admin web interface, checking for Pexip-related services running on the network, or reviewing infrastructure documentation for conferencing platform installationsAffected if Pexip Infinity conferencing platform is present in the environment
-
Identify the installed versionLog into the Pexip Infinity admin interface and navigate to the Dashboard or System > Administration page to view the current software version. Alternatively, check the version via CLI if accessibleAffected if The installed version is lower than 32.0 (e.g., 31.x, 30.x, etc.)
-
Verify Webapp1 component is activeCheck if the Webapp1 component is enabled by reviewing the Pexip Infinity deployment configuration in the admin interface under Call Routing or Web App settings. Confirm that users can access the web-based conferencing interfaceAffected if Webapp1 component is enabled and accessible to users (this is the component containing the vulnerability)
-
Check for preconfigured link configurationReview the Pexip Infinity admin interface for any preconfigured meeting links, call templates, or customized URL configurations under Call Routing, Deployment settings, or any custom link generation featuresAffected if Preconfigured links are created or used in the deployment, as this is the attack vector for the XSS vulnerability
The environment is affected if Pexip Infinity version is below 32.0, the Webapp1 component is active, and preconfigured links are used, allowing attackers to inject malicious scripts through crafted links.
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.
dbcve · scoped32.0
Upgrade Pexip Infinity to version 32 or later. Until patched, exercise caution with preconfigured links and implement Content Security Policy headers to mitigate XSS risks.
Pexip Infinity 32.0
- Upgrade Pexip Infinity to version 32.0 or later to resolve the Webapp1 XSS vulnerability via preconfigured links
Generated from the published advisory — verify against the referenced sources before acting.
- 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-37225 — 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-37225 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