Bpmn.ioWordPress extension · Camunda
CVE-2024-51577
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 · uneditedImproper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in neville.lugton bpmn.io bpmnio allows Stored XSS.This issue affects bpmn.io: from n/a through <= 1.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 confidenceStored XSS vulnerability in bpmn.io library allows attackers to inject malicious JavaScript code through unsanitized input that gets persisted and executed when other users view the affected web pages. The flaw stems from improper neutralization of user-supplied data during page generation.
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
Bpmn.ioWordPress extension
= 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
- Low
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/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 bpmn.io library usageSearch your codebase for bpmn.io imports, package.json dependencies, or loaded bpmn.io scripts. Common patterns: 'bpmn-js', 'bpmn.io', or look in node_modules for bpmn-related packages.Affected if bpmn.io library is present in your dependencies or loaded scripts
-
Check installed bpmn.io versionRun 'npm list bpmn-js' or inspect your package-lock.json / package.json to find the exact version of bpmn-js or bpmn.io packages.Affected if The installed version is exactly 1.0 (version = 1.0)
-
Identify user input paths to bpmn.ioReview your code for places where user-controlled data (form inputs, API parameters, uploaded files) flows into bpmn.io diagram properties, labels, or element attributes. Search for function calls that pass user data to bpmn.io setters or modelers.Affected if User-supplied data is being passed to bpmn.io components without prior sanitization
-
Inspect data rendering in bpmn.io viewerExamine how bpmn.io renders diagram elements. Look for places where diagram properties (names, descriptions, documentation, or custom extension elements) are displayed in the UI without context-aware output encoding.Affected if Diagram data from users is rendered in the UI without proper escaping or sanitization on output
You are affected if you are using bpmn.io version 1.0 AND your application accepts user input that gets persisted in BPMN diagrams and rendered to other users without sanitization.
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 robust input validation combined with context-aware output encoding/escaping for all user-controlled data rendered in the bpmn.io interface to prevent script execution.
Fix this in Bpmn.io
Scoped from the published advisory
- Consultation3.0 h
- Implementation8.0 h
- Testing4.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 $4,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-51577 — 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-2024-51577 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