Skip to main content
Menu
CVEs

CVE

Frappe server-side request forgery in get_email_html

CVE-2026-130069

CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:L/SI:N/SA:N

5.3MediumCNA
Exploited
No known exploitation
Fix
Fixed in 15.123.0, 16.50.0
Who is exposed
Not reported

Do first: Upgrade to a fixed version: 15.123.0, 16.50.0.

Published
Last modified
Reference
Last checked
18/100 · provisional
100% of frappe downloads last week were affected versions (771).PyPI, per-version counts from ClickPy, 771 downloads in the last 7 days, read Nov 14, 2026
None on Exploit-DB, Metasploit or GitHub

Summary

Frappe Framework has a server-side request forgery flaw in the get_email_html method, which lacks role checks. A remote attacker with a low-privilege login, including portal Website Users, can inject stylesheet link tags into unescaped email templates, causing the server to fetch internal or external hosts and return their content.

Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.

Original description

Frappe Framework before 15.123.0 and 16.x before 16.50.0 contains a server-side request forgery vulnerability in the frappe.email.email_body.get_email_html method, which lacks role checks. Authenticated users, including portal Website Users, can inject stylesheet link tags into unescaped email templates, causing Premailer to fetch internal or external hosts and return the content.

cve.now Index

18Pcve.now Index 18 of 100 · methodology v3 · provisional
  • Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
  • Exposure3/25Reachable over the network · Unknown: No advisory context yet
  • Reach10/20Affects PyPI packages
  • Severity5.3/10CVSS 5.3
  • No patch0/5No signal

What would change the score

  • Would score about 73 if added to CISA KEV
  • Would score about 68 if CISA's SSVC rates exploitation active
  • Would score about 37 if advisories confirm default setups are exposed

Impact

  • Widely used

    frappe has 697 weekly downloads.Source: pypistats.org

    1 packages depend on frappe.Source: deps.dev

What to do

  • Upgrade to a fixed version: 15.123.0, 16.50.0.

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-130069 (Frappe Framework before 15.123.0 and 16.x before 16.50.0 SSRF via get_email_html), 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-130069 (entry last updated 2026-11-16):
Affected:
- PyPI package frappe: fixed in 15.123.0; from 16.0.0, fixed in 16.50.0
Fixed versions: 15.123.0, 16.50.0.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-130069 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-130069 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Packages (PyPI): find every lockfile in each project and run the stack.check operation of the cve.now MCP server (execute) on each one. Compare the resolved versions, not the ranges a manifest declares, with the affected versions above. Include transitive dependencies.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/frappe/frappe/pull/43688
- https://github.com/frappe/frappe/commit/5787684f0ad0352f414436d6f39479a9f35d3d9b
- https://github.com/frappe/frappe/commit/887d027ffd9bb48544a7f68c3762670a480cb9e2
- https://github.com/frappe/frappe/blob/v15.121.1/frappe/email/email_body.py#L420-L452
- https://github.com/frappe/frappe/releases/tag/v15.123.0
- https://github.com/frappe/frappe/releases/tag/v16.50.0
- https://www.vulncheck.com/advisories/frappe-framework-before-15.123.0-and-16-x-before-16.50.0-ssrf-via-get-email-html
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-130069
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-130069"}.

Timeline

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

Affected versions

  • frappePyPI

    fixed in 15.123.0; From 16.0.0 · fixed in 16.50.0

    No fix released. The advisory names 15.123.0 and 16.50.0 as the fix, which the registry doesn't have yet. The latest release, 0.0.1, is still affected.

Evidence 9

CVE record · 2

Establishes: The identifier and description.

  1. Record
  2. Record

Other links · 7

  1. Patch
  2. Patch
  3. Patch
  4. Repository
  5. Repository
  6. Repository
  7. Link

Corrections

None so far.

Something wrong on this page? Report an error. Every fix is listed here.

Questions about CVE-2026-130069

Is CVE-2026-130069 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-130069?

frappe (PyPI): before 15.123.0; from 16.0.0 before 16.50.0.Source: cve.now feed data

How do I fix CVE-2026-130069?

Upgrade to a fixed version: 15.123.0, 16.50.0.Source: cve.now feed data