Frappe comment spoofing in add_comment handler
- Exploited
- No known exploitation
- Fix
- Fixed in 15.108.0, 16.18.3
- Who is exposed
- Not reported
Summary
Frappe, a full-stack web application framework, has a flaw in its add_comment handler that trusts the commenter's name and email fields sent by the client. Remotely, without logging in, an attacker can post a comment that appears to come from another person's name or email address.
Written by a model
Original description
Frappe is a full-stack web application framework. Prior to 15.108.0 and 16.18.3, the add_comment handler in frappe/templates/includes/comments/comments.py trusts the client-provided comment_by and comment_email fields. A caller can submit chosen identity metadata that is stored with a comment, causing the comment to appear to originate from another name or email address. This issue is fixed in versions 15.108.0 and 16.18.3.
What to do
Upgrade to a fixed version: 15.108.0, 16.18.3.
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-47278 (Frappe: Comment Spoofing via add_comment), 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-47278 (entry last updated 2026-11-19):
Affected:
- frappe frappe: fixed in 15.108.0; from 16.0.0, fixed in 16.18.3
Fixed versions: 15.108.0, 16.18.3.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-47278 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-47278 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/frappe/frappe/security/advisories/GHSA-89m3-vggh-725v
- https://github.com/frappe/frappe/pull/39373
- https://github.com/frappe/frappe/pull/39379
- https://github.com/frappe/frappe/pull/39380
- https://github.com/frappe/frappe/commit/2d930e2d3747012cc8a8c8fbdccaf8c2c5070391
- https://github.com/frappe/frappe/commit/7bcbf72f283fc68d9abe783fcc2219386f14e9ef
- https://github.com/frappe/frappe/commit/c1cc4cc4ef3ac2151fff330edd32aa96c13d4118
- https://github.com/frappe/frappe/releases/tag/v15.108.0
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-47278
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-47278"}.Affected versions
- frappe frappefixed in 15.108.0; From 16.0.0 · fixed in 16.18.3
cve.now Index
- Exploitation0/40No signal
- Exposure17/25No login or user action needed per the CVSS vector, reachable over the network without a login · Unknown: No advisory context yet
- Reach?/20Unknown. No tracked technology or package matched
- Severity6.9/10CVSS 6.9
- No patch0/5No signal
What would change the score
- Would score about 69 if added to CISA KEV
- Would score about 64 if CISA's SSVC rates exploitation active
- Would score about 29 if advisories confirm default setups are exposed
Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Evidence 11
| Kind | Source |
|---|---|
| Vendor advisory 1Establishes: Affected and fixed versions. | |
| Advisory | GitHub · frappe/frappe · Advisory GHSA-89m3-vggh-725v |
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-47278 |
| Record | NVD · CVE-2026-47278 |
| Other links 8 | |
| Repository | GitHub · frappe/frappe · Pull request #39373 |
| Repository | GitHub · frappe/frappe · Pull request #39379 |
| Repository | GitHub · frappe/frappe · Pull request #39380 |
| Repository | GitHub · frappe/frappe · Commit 2d930e2d |
| Repository | GitHub · frappe/frappe · Commit 7bcbf72f |
| Repository | GitHub · frappe/frappe · Commit c1cc4cc4 |
| Repository | GitHub · frappe/frappe · Release v15.108.0 |
| Repository | GitHub · frappe/frappe · Release v16.18.3 |
Questions about CVE-2026-47278
Is CVE-2026-47278 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-47278?
frappe: before 15.108.0; from 16.0.0 before 16.18.3.
Source: cve.now feed data
How do I fix CVE-2026-47278?
Upgrade to a fixed version: 15.108.0, 16.18.3.
Source: cve.now feed data
Related
- CVE-2026-126315Frappe HRMS 16.14.0 before 16.20.1 Telemetry Setting Bypass Information Exposure
- CVE-2026-126314Frappe HRMS 15.0.0 before 15.64.6 Missing Authorization in Bulk Record Creation
- CVE-2026-126317Frappe HRMS 16.0.0 before 16.20.1 Missing Authorization in Company Details Endpoint
- CVE-2026-126412Frappe HRMS 15.0.0 before 15.64.1 Missing Authorization in Bulk Record Action
- CVE-2026-126414Frappe HRMS 15.0.0 before 15.64.2 Missing Authorization in Record Update Endpoints
- CVE-2026-130787Frappe ERPNext before 16.35.0 Missing Authorization in Financial Reporting Endpoints
No corrections so far. Something wrong on this page? Report an error.