Skip to main content
Menu
CVEs

Pydici stored XSS via contact name in relation diagram

CVE-2026-133871Published , updated

5.1MediumCNA
Exploited
No known exploitation
Fix
Fix or patch referenced
Who is exposed
Not reported

Summary

Pydici, a product from digitalfox, has a stored cross-site scripting flaw in its contact detail relation diagram. An attacker who has permission to edit contacts can save malicious HTML as a contact name, and the script runs in the browser of a user who views that contact, which requires that user to take an action.

Written by a model

Original description

Pydici through 2026.11.1 contains a stored cross-site scripting vulnerability that allows authenticated users to inject script by storing HTML in contact names rendered unescaped in the contact detail mermaid diagram. Attackers with contact edit permission can store malicious markup that Contact.relationData() interpolates and contact_detail.html renders with the safe filter, executing script in victims' sessions.

What to do

Apply the patch listed under Evidence.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-133871 (Pydici through 2026.11.1 Stored XSS via Contact Name in Relation Diagram), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-133871 (entry last updated 2026-11-20):
Affected:
- digitalfox pydici: through 2026.11.1
Fixed versions: none listed yet.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-133871 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-133871 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/digitalfox/pydici/commit/2d71a58df112cfe697c829af79ce7c5c402f876b
- https://github.com/digitalfox/pydici/issues/234
- https://github.com/digitalfox/pydici
- https://github.com/digitalfox/pydici/blob/v2026.11.1/crm/models.py#L223-L229
- https://github.com/digitalfox/pydici/blob/v2026.11.1/templates/crm/contact_detail.html#L44-L47
- https://www.vulncheck.com/advisories/pydici-through-2026.11.1-stored-xss-via-contact-name-in-relation-diagram
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-133871
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-133871"}.

Affected versions

cve.now Index

8Pof 100 · provisional · methodology v3
  • Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
  • Exposure3/25Reachable over the network · Unknown: No advisory context yet
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity5.1/10CVSS 5.1
  • No patch0/5No signal

What would change the score

  • Would score about 63 if added to CISA KEV
  • Would score about 58 if CISA's SSVC rates exploitation active
  • Would score about 27 if advisories confirm default setups are exposed

Timeline

  1. CVE published
  2. First seen by cve.now

Evidence 8

Questions about CVE-2026-133871

Is CVE-2026-133871 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: cve.now feed data

Which versions are affected by CVE-2026-133871?

pydici: through 2026.11.1.

Source: cve.now feed data

No corrections so far. Something wrong on this page? Report an error.