High Injection

CVE-2026-114664 — Frappe before 16.33.0 Blind SQL Injection via get_events

Frappe Framework before 16.33.0 contains a blind SQL injection vulnerability in the frappe.desk.doctype.event.event.get_events method, which fails to properly neutralize user-supplied input before including it in SQL queries. Authenticated attackers can send crafted input to get_events and infer query results from application behavior to extract sensitive database information.

Published Oct 21, 2026 · Updated Oct 22, 2026 · Sources: CVE Program (cve.org) e CISA ADP, NIST National Vulnerability Database · CNA: VulnCheck

Low

Who exploits it and how urgent it is

A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.

No exploitation signal in the sources consulted so far.

How the score was calculated

EPSS 0.2% (30-day exploitation probability)+1
Technical severity (high)+6

The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.

Exploitation

Not confirmed

Not in CISA KEV — an absence of record, not proof it is unexploited.

EPSS FIRST

0.2%

ahead of 10% of scored CVEs · Oct 27, 2026

Affects

Frappe

CVSS base

7.1

High · 2 source(s)

Remediation

Fixes and mitigations documented by the sources — linked to the original advisory.

No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.

First 24 hours

Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.

Identify exposed assets running the affected vendor/product/version combinations (Frappe Frappe).
No fix documented in the sources: reduce exposure and monitor the vendor advisory.
Search available logs for exploit probes matching the vulnerability class (injection), errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

Vendor	Product	Versions	Status	Source
Frappe	Frappe	< 16.33.0	Vulnerable	CVE Program (cve.org) e CISA ADP

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Attack vector

Network

Attack complexity

Low

Privileges required

Low

User interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

Low

Availability

None

Every base score collected

Sources score independently and may disagree; each row says who scored it and under which version.

Score	Version	Severity	Expl.	Impact	Scored by
7.1	CVSS 4.0	High	—	—	disclosure@vulncheck.com via NIST National Vulnerability Database
7.1	CVSS 4.0	High	—	—	VulnCheck via CVE Program (cve.org) e CISA ADP
7.1	CVSS 3.1	High	2.8	4.2	disclosure@vulncheck.com via NIST National Vulnerability Database
7.1	CVSS 3.1	High	—	—	VulnCheck via CVE Program (cve.org) e CISA ADP

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:N (score shown at the top: disclosure@vulncheck.com)

Weakness MITRE

Weakness class according to MITRE’s CWE catalog.

CWE-89 · SQL Injection

Other CVEs with this weakness →

EPSS over time FIRST

Oct 22, 2026 → Oct 27, 2026 · 6 reading(s) · max 0.20%

Detection

Read off the CVSS vector and the weakness class. Starting points, not tested rules.

Prioritize edge telemetry for the network-reachable component (proxy, WAF, IDS/IPS).
Look for parameters with command/query metacharacters and unexpected child processes of the service.

web/proxy/WAF logsnetwork IDS/IPSapplication logsendpoint telemetry (EDR)

Timeline

What happened to this CVE, newest first.

2026
Source status changed · Published → Deferred
Oct 22, 2026 · NIST National Vulnerability Database
Record published
Oct 22, 2026
CVSS changed · 7.1
Oct 22, 2026 · CVE Program (cve.org) e CISA ADP
Source status changed · → Published
Oct 22, 2026 · CVE Program (cve.org) e CISA ADP
Record created in this database
Oct 22, 2026 · CVE Program (cve.org) e CISA ADP
CVE published
Oct 21, 2026 · VulnCheck

Source activity

Repeated readings are counted rather than listed.

1× Official description updated · Oct 22, 2026 – Oct 22, 2026

References

2 on the record

github.com/frappe/frappe/security/advisories/GHSA-p4w2-9mr5-6prj
vendor-advisory, CVE Program (cve.org) e CISA ADP
www.vulncheck.com/advisories/frappe-before-16.33.0-blind-sql-injection-via-get-events
third-party-advisory, CVE Program (cve.org) e CISA ADP

Elsewhere on this site

Frappe
every CVE for this vendor

Injection
same class

CWE-89
other pages naming this weakness

Related CVEs (same products)

Medium CVE-2026-111388 Frappe before 16.33.0 restrict_ip Allowlist Bypass via API Key, OAuth Authentication 12d
Medium CVE-2026-66057 Frappe: Open Redirect via Unsanitized OAuth State Param. 14d
High CVE-2026-55823 Frappe: Possibility of SQL injection in reportview 14d
Low CVE-2026-109603 Frappe Framework before 16.17.0 Authenticated SSRF and LFI via pdfkit 15d
Medium CVE-2026-109602 Frappe before v16.31.0 Stored XSS via Dashboard Chart Filters 15d
Medium CVE-2026-109598 Frappe before 16.33.0 Broken Authorization via send_sms Endpoint 15d

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

No fixed version, patch or mitigation documented.
No CISA SSVC assessment.
No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record

Text assembled only from the fields above — no additional claims.

What should defenders know first?

CVE-2026-114664 is "Frappe before 16.33.0 Blind SQL Injection via get_events", rated High. It affects Frappe (Frappe); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 7.1 describes technical severity. EPSS 0.20% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.

Comments

Moderated technical discussion. Read the community guidelines.

No comments yet.