BottleCRM CVE-2026-110592

Requires an authenticated account with organization-member privileges that can create or edit invoices, AND the target must use a custom invoice template processed by render_invoice_template() (the HTML is injected via notes, terms, client name, or client address fields). Exploitation further depends on a victim viewing the rendered PDF - delivered by download, public link, or email (UI:P) - so it is a passive-interaction, fraud-oriented flaw rather than automatic server-side compromise. Limiting factors: valid credentials (PR:L) and the custom-template rendering path are prerequisites; default configurations not using custom templates or not exposing PDFs to external recipients substantially reduce realistic risk.

This is a genuinely medium/low-priority issue, not an inflated high-CVSS finding. The vendor-supplied CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:L/UI:P/VC:N/VI:L/VA:N) scores only 5.1, and the metrics are internally consistent with the description: network-reachable but requiring valid low-level authentication (PR:L - an organization member) and passive user interaction (UI:P - a victim must open/view the resulting PDF). Impact is limited to integrity (VI:L) with no confidentiality or availability effect, which matches CWE-116 output-encoding abuse rather than code execution or data theft. No EPSS score, CISA KEV listing, or public POC was provided in the input, so exploitation pressure appears low: this maps to 'no public exploit identified at time of analysis.' The realistic threat is social-engineering/fraud (forged invoice totals, payee and payment instructions) rather than server compromise. One signal to verify: the CPE identifies the product as micropyramid:bottlecrm, but all three references point to the Django-CRM/Django-CRM repository - confirm with the vendor whether BottleCRM and Django-CRM are the same codebase before acting on version ranges.

A low-privileged but trusted member of an organization edits an invoice's notes, terms, client name or address fields, embedding HTML and CSS that the custom-template renderer in render_invoice_template() does not escape. When the generated PDF is downloaded, shared via a public link, or emailed to a client, the injected markup overlays the real totals, payee, and payment instructions, producing a fraudulent-but-authentic-looking invoice. No public exploit code was identified in the provided data; exploitation requires an authenticated account and a victim who opens the PDF (UI:P).