dbcve.org
Cross-Site Request Forgery (CSRF)Weakness · CWE-352

CVE-2026-49433

MEDIUM · 5.0 CVSS v3.1 Published 2026-06-01
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
57/100
Remediation priority · Elevated
Remotely reachable No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
The DeepAI endpoint 'https://api.deepai.org/change_user_email' accepts POST requests without any CSRF protection. If an attacker can trick a logged-in user into clicking a malicious link, the attacker can change the user's email address and take over their account. Fixed on 2026-05-20.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The DeepAI endpoint 'https://api.deepai.org/change_user_email' accepts POST requests without CSRF protection. An attacker can trick a logged-in user into clicking a malicious link, allowing the attacker to change the user's email address and potentially take over the account.

MitigationEnsure the DeepAI service is updated to the patched version released on 2026-05-20, which should include proper CSRF token validation for email change operations.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
High
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:L/A:L

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify CSRF token requirement on email change endpoint
    Send a POST request to https://api.deepai.org/change_user_email with valid authentication but without a CSRF token parameter. Inspect the response to see if the request is processed or rejected based on token absence.
    Affected if The request succeeds or returns a success status without requiring a token, indicating no CSRF protection.
  2. Inspect Origin and Referer header validation
    Send a POST request to the email change endpoint with a mismatched or missing Origin/Referer header. Check if the server accepts or rejects the request based on header validation.
    Affected if The server accepts requests with arbitrary or missing Origin/Referer headers without validation.
  3. Check session cookie SameSite attribute
    Inspect the session cookies returned by DeepAI (via browser dev tools or curl -I). Look for the SameSite attribute on cookies associated with the DeepAI domain.
    Affected if Session cookies lack the SameSite attribute or have it set to 'None' without Secure flag.
  4. Test cross-origin request forgery
    From a different origin (e.g., a test HTML page on localhost), attempt to trigger a POST to https://api.deepai.org/change_user_email on behalf of an authenticated user. Observe if the action completes.
    Affected if The cross-origin request successfully changes the email address without being blocked by CORS or CSRF defenses.

You are affected if the /change_user_email endpoint processes requests without validating CSRF tokens, Origin/Referer headers, or enforcing SameSite cookies on the session.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Ensure the DeepAI service is updated to the patched version released on 2026-05-20, which should include proper CSRF token validation for email change operations.

Recommended fix Moderate confidence
  1. This is a server-side vulnerability that DeepAI has already fixed as of 2026-05-20.
  2. No user action is required for remediation; the CSRF protection was implemented on DeepAI's API servers.
  3. If you are a DeepAI user concerned about account security, verify that two-factor authentication is enabled on your account as an additional safeguard.
  4. Report any suspicious account changes to DeepAI support immediately.

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,800
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,480.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-49433 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-49433 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data