SEPTEMBER 7, 2026
Live Feed
Back to database
Case File

CVE-2026-71378

MEDIUM · CVSS 4.6 EPSS 0.25%

Source: NVD + CISA KEV + EPSS · Published 2026-08-31 · Last synced 2026-09-07

CyberRota Analysis

AI-Generated

Apache Wicket versions 9.1.0 to 9.23.0 and 10.0.0 to 10.10.0 are vulnerable to cross-site request forgery (CSRF) due to unsafe allowances in the FetchMetadataResourceIsolationPolicy, which can allow malicious actors to exploit authenticated sessions through crafted GET requests. This vulnerability can lead to unauthorized actions being executed on behalf of users, particularly if an attacker controls a sibling origin or has access to a subdomain. Organizations using affected versions should prioritize upgrading to versions 9.24.0 or 10.11.0 to mitigate this risk.

CVE
CVE-2026-71378
Severity
MEDIUM
CVSS
4.6
EPSS
0.25%
Apache

Original NVD Description

ResourceIsolationRequestCycleListener protects a Wicket application against cross-site request forgery by rejecting requests that a resource isolation policy judges to come from another origin. Its default policy, FetchMetadataResourceIsolationPolicy, was derived from a reference implementation written to guard static resources, and it inherited two allowances that are unsafe when the thing being guarded is an action on a page: * Every "simple top-level navigation" was allowed. Any GET request carrying Sec-Fetch-Mode: navigate whose Sec-Fetch-Dest was neither object nor embed was allowed, whatever Sec-Fetch-Site said — including cross-site. Wicket invokes component listeners (Link.onClick(), form submits, behaviour callbacks) through ordinary GET navigations, so a page under an attacker's control could navigate the victim's browser to a listener URL and have that listener run inside the victim's authenticated session. Browsers send SameSite=Lax cookies — the effective default when no SameSite attribute is set — on cross-site top-level GET navigations, so the victim's session cookie accompanied the request. * Sec-Fetch-Site: same-site was allowed unconditionally. That value means the same registrable domain and scheme but a different origin — another subdomain or another port. Any sibling origin could therefore invoke any listener by any method, POST form submits included, and cookies are always sent on same-site requests regardless of SameSite. A hostile sibling origin obtained through a subdomain takeover, through delegated user content, or through an XSS elsewhere on the site could act as the authenticated user. Users are recommended to upgrade to version 9.24.0 or 10.11.0, which fix the issue. Affected versions * Apache Wicket 9.1.0 through 9.23.0 * Apache Wicket 10.0.0 through 10.10.0 Not affected Any release older than 9.1.0: * Apache Wicket 8.x (8.0.0 through 8.17.0). The resource isolation classes do not exist in the 8.x line, which offers only the Origin/Referer-based CsrfPreventionRequestCycleListener. No 8.x release requires a fix. * Apache Wicket 9.0.0. ResourceIsolationRequestCycleListener and FetchMetadataResourceIsolationPolicy were introduced by WICKET-6786 and first shipped in 9.1.0 (released 2020-10-07).

Related CVEs

Other vulnerabilities affecting the same vendor(s)