Appsmith: Configuration-dependent origin validation bypass in password reset and email verification link generation

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

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

EPSS

No dated EPSS signal available.

As published by the source; long descriptions are shortened.

Summary A configuration-dependent origin validation bypass was identified in Appsmith’s password reset and email verification flows on current release. Both flows derive the email-link base URL from the request Origin header. The current validation only enforces a trusted base URL when APPSMITHBASEURL is configured. If that setting is unset, the application accepts the caller-supplied origin and uses it to generate token-bearing reset and verification links. On deployments with email delivery enabled and APPSMITHBASEURL unset, this can cause Appsmith to send security-sensitive links whose clickable host is attacker-controlled, which can plausibly lead to account takeover after victim interaction. Details The current release head at commit e77639eca4974469c1e676904851ffdaedd38111 was reviewed. The relevant routes are publicly reachable in SecurityConfig.java: - POST /forgotPassword is permitted without authentication at line 209 - POST /resendEmailVerification is permitted without…

Published by the source

12 Jun 2026, 18:28 UTC

Last modified by the source

12 Jun 2026, 18:28 UTC

Source last checked

26 Oct 2026, 16:46 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-j9gf-vw2f-9hrw

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: GHSA-j9gf-vw2f-9hrw

Advisory: Appsmith: Configuration-dependent origin validation bypass in password reset and email verification link generation
IDs: GHSA-j9gf-vw2f-9hrw
Record: https://patchnext.com/advisories/ghsa-j9gf-vw2f-9hrw (revision 1, source checked 26 Oct 2026, 16:46 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 8.1)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: com.appsmith:server 2.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- Maven com.appsmith:server: affected < 2.0; fixed in 2.0

## Suggested inspection (read-only)
- Maven com.appsmith:server: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on com.appsmith:server.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-j9gf-vw2f-9hrw (GitHub-reviewed advisory GHSA-j9gf-vw2f-9hrw lists affected ranges: Maven com.appsmith:server >=0 <2.0)

Commands are suggestions: review each one before running it.