CVE-2026-49433: api.deepai.org · Cross-Site Request Forgery (CSRF)
Affects api.deepai.orgSource CVE Database V5
Not known to be exploited · CVSS 2.3 Low : upgrade to 2026-05-20 when convenient.
Data as of 30 Oct 2026, 06:59 UTC
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 1% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 2026-05-20
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:P/VC:L/VI:L/VA:L/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 1 Jun 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.
What to do
Upgrade api.deepai.org to 2026-05-20.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| DeepAIapi.deepai.org | Affected
| Fixed in
|
AI-suggested
The description indicates the vulnerability was fixed on 2026-05-20, but no official vendor advisory or patch link is provided. Users and administrators should verify that their DeepAI API endpoints are updated to the fixed version released after this date. Since this is not a cloud service, remediation depends on applying the fix.
Description
CVE-2026-49433 is a Cross-Site Request Forgery (CSRF) vulnerability in the DeepAI API endpoint 'https://api.deepai.org/change_user_email'. The endpoint accepts POST requests without CSRF protection, allowing an attacker to potentially change a logged-in user's email address by tricking them into clicking a malicious link. This could lead to account takeover. The vulnerability has a low CVSS score of 2.3 and was fixed on 2026-05-20. No known exploits are reported in the wild. Patch status is not explicitly confirmed in the provided data.