Home/CVE/Frappe is a full-stack web application framework. Prior to versions 15.107.0 and 16.17.0, lack of validations in the "su
CVE
CVE-2026-44208
Frappe is a full-stack web application framework. Prior to versions 15.107.0 and 16.17.0, lack of validations in the "su
Frappe is a full-stack web application framework. Prior to versions 15.107.0 and 16.17.0, lack of validations in the "submit_discussion()" endpoint allows for unauthorized access to resources. This issue has been patched in versions 15.107.0 and 16.17.0.
EPSS 0.00049
Schedule remediation
- SSVC automatable: yes - attacks can be scripted at scale
- ⚠ NVD has not scored this CVE yet - manual triage required (common for recent CVEs)
Sigma rules0
YARA rules0
Look this up elsewhere - one-click external pivots
▸
How to read a CVE - triage first, then detect and patch
This page is every public fact about CVE-2026-44208, cross-linked. Its job is to answer one question fast - does this need my attention now? - and then hand you the two things you do about it. Here is how an analyst reads it.
Triage: should I act now? Four signals, and they are not interchangeable:
CVSSseverity - how bad it is IF exploited, 0-10. A high CVSS alone is not urgency; a flaw can be a perfect 10 and never actually be attacked.
EPSSprobability - a model’s estimate of the chance it is exploited in the next 30 days, 0-1. This is the “will it actually happen” signal.
CISA KEVconfirmed - it is being exploited in the wild right now. The strongest signal on the page; KEV beats any score.
Weaponisedavailability - public exploits / PoCs, and especially Metasploit modules rated Excellent / Great. Reliable, packaged exploit code means low-skill attackers can use it today.
How they combine: KEV, or a dependable Metasploit module, means patch now regardless of CVSS. High CVSS + low EPSS + no exploit is real but not an emergency - schedule it. Low CVSS but KEV-listed still gets patched now. The verdict above already weighed these for you; this is how it got there.
Then what - two workflows:
Detectwhen you cannot patch today, follow this CVE to the ATT&CK techniques it enables, then Build a SIEM detection (the green button) - author a rule, test it in Atomic, deploy it. That buys visibility while the patch waits.
PatchAffected products / packages tell you if you are exposed; Fixed versions by distribution and Vendor advisories give the exact version that closes it.
Reading order for the panels below: verdict + badges, then Public exploits / Metasploit (is it weaponised), then ATT&CK techniques + Sigma / IDS rules (can I detect it), then Affected products / packages + Fixed versions (am I exposed, what patches it), then Threat actors / IOCs (who uses it), then Scoring & timeline / references (the evidence).
◆
ATT&CK techniques
20Techniques this CVE enables - linked via CWECAPECATT&CK. High◆ = named directly in ATT&CK or Nuclei templates.
T1005 · Data from Local System T1012 · Query Registry T1014 · Rootkit T1027.009 · Embedded Payloads T1037 · Boot or Logon Initialization Scripts T1080 · Taint Shared Content T1083 · File and Directory Discovery T1134.001 · Token Impersonation/Theft T1505.005 · Terminal Services DLL T1542.003 · Bootkit T1543 · Create or Modify System Process T1543.001 · Launch Agent T1543.003 · Windows Service T1543.004 · Launch Daemon T1546.001 · Change Default File Association T1546.004 · Unix Shell Configuration Modification T1546.008 · Accessibility Features T1546.016 · Installer Packages T1547 · Boot or Logon Autostart Execution T1547.006 · Kernel Modules and Extensions
▤ Build a SIEM detection for these techniques
▤
CAPEC attack patterns
12Attack patterns this CVE enables - the bridge from weakness to ATT&CK technique.
CAPEC-CAPEC-1 · Accessing Functionality Not Properly Constrained by ACLs CAPEC-CAPEC-104 · Cross Zone Scripting CAPEC-CAPEC-127 · Directory Indexing CAPEC-CAPEC-13 · Subverting Environment Variable Values CAPEC-CAPEC-17 · Using Malicious Files CAPEC-CAPEC-19 · Embedding Scripts within Scripts CAPEC-CAPEC-39 · Manipulating Opaque Client-based Data Tokens CAPEC-CAPEC-402 · Bypassing ATA Password Security CAPEC-CAPEC-441 · Malicious Logic Insertion CAPEC-CAPEC-45 · Buffer Overflow via Symbolic Links CAPEC-CAPEC-478 · Modification of Windows Service Configuration CAPEC-CAPEC-479 · Malicious Root Certificate
⬡
Weakness Classification
CWE-284Improper Access Control
CWE-285Improper Authorization
▣
Scoring & Timeline
SSVC triage · cisa-vulnrichment
Exploitation
none
Automatable
yes
Technical impact
partial
SSVC asks the questions that actually drive patch urgency: is it being exploited, can attacks be automated, and how total is the impact.