dbcve.org
Cross-site Scripting (XSS)Weakness · CWE-79

CVE-2026-41653

HIGH · 7.0 CVSS v4.0 Published 2026-05-07
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
77/100
Remediation priority · High
Remotely reachable No privileges

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 · unedited
BentoPDF is a client-side PDF toolkit that is self hostable. Prior to version 2.8.3, a cross-site scripting vulnerability was identified in BentoPD. An attacker may be able to execute arbitrary JavaScript in certain circumstances in Markdown to PDF Tool. This issue has been patched in version 2.8.3.

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 confidence

Cross-site scripting (XSS) vulnerability in BentoPDF's Markdown to PDF conversion feature allows attackers to inject malicious JavaScript that executes when victims process crafted Markdown content. The vulnerability exists in versions prior to 2.8.3 and is triggered through the Markdown input processing pipeline.

MitigationUpgrade to BentoPDF version 2.8.3 or later to apply the security patch. If immediate upgrade is not feasible, restrict or disable the Markdown to PDF tool until the patch can be deployed.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS 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
Authentication
X
User interaction
A
Scope
X

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/VC:H/VI:L/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify BentoPDF installation and version
    Locate the BentoPDF application and retrieve its installed version number (typically found in the application menu, about dialog, or via command line if applicable)
    Affected if The installed version is lower than 2.8.3
  2. Verify the Markdown to PDF feature is accessible
    Check whether the Markdown to PDF conversion functionality is present and accessible in the BentoPDF interface or via available conversion options
    Affected if The Markdown to PDF conversion feature exists and is available for use
  3. Confirm Markdown input processing is in use
    Determine if the BentoPDF environment processes Markdown files or content as part of normal document workflows
    Affected if Markdown files are being processed through BentoPDF's conversion pipeline
  4. Compare version against the patched release
    Compare the identified BentoPDF version number against the fixed version 2.8.3
    Affected if The installed version is any release prior to 2.8.3

A user is affected if BentoPDF is installed with a version lower than 2.8.3 AND the Markdown to PDF conversion feature is enabled or being used to process content.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to BentoPDF version 2.8.3 or later to apply the security patch. If immediate upgrade is not feasible, restrict or disable the Markdown to PDF tool until the patch can be deployed.

Recommended fix Moderate confidence

2.8.3

  1. 1. Identify the BentoPDF deployment method used (Docker, npm, or direct installation)
  2. 2. For Docker deployments: Pull the latest image or update the image tag to the version containing the fix
  3. 3. For npm installations: Run 'npm update' or specify version 2.8.3 in package.json
  4. 4. For direct installations: Download version 2.8.3 from the official repository
  5. 5. Restart the BentoPDF service after updating
  6. 6. Verify the update was successful by checking the application version
  7. 7. Test the Markdown to PDF functionality to confirm the XSS vulnerability is remediated

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,664.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-41653 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-41653 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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