Severity: important
CVSS 4.0: 6.9 (medium)
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N
Affected versions:
- Apache Wicket (org.apache.wicket:wicket-core) 8.0.0 through 8.19.0
- Apache Wicket (org.apache.wicket:wicket-core) 9.0.0 through 9.24.0
- Apache Wicket (org.apache.wicket:wicket-core) 10.0.0 through 10.11.0
Description:
Missing authorization in Apache Wicket.
org.apache.wicket.core.request.handler.ListenerRequestHandler invokes an
IRequestListener only when org.apache.wicket.Component#canCallListener() allows
it, and that method is isEnabledInHierarchy() && isVisibleInHierarchy(). The
visibility half reads a flag that carries the outcome of
IAuthorizationStrategy#isActionAuthorized() for the Component.RENDER action,
and that flag is written in one place only, Component#configure(), during the
render phase. A listener URL built by a subclass of
org.apache.wicket.core.request.mapper.AbstractBookmarkableMapper carries the
page identifier and the component path in a single parameter, and the page
identifier may be empty. When it is, a new page instance is constructed,
PageProvider#wasExpired() is false because no identifier was supplied, and
PageAndComponentProvider#getComponent() finds the component directly on the new
instance, so neither a render pass nor Component#configure() runs before the
listener is invoked. The flag therefore still holds its constructor default,
the component counts as visible, and the listener of a component the
authorization strategy denied RENDER for is executed. The same request also
skips Component#onConfigure(), so visibility and enablement an application sets
there are not applied either.
There are two ways to reach this, and neither requires anything but a request.
On a page that is stateful, the caller omits the page identifier from a
listener URL that would otherwise carry it. On a page that Wicket considers
stateless, nothing has to be altered at all: Wicket itself writes listener URLs
without a page identifier for such pages, and a component the strategy denies
RENDER for is treated as stateless and therefore does not keep the page
stateful, so denying RENDER can itself produce the page-id-less form. The
second route has never been refused. The ENABLE decision of
IAuthorizationStrategy is consulted on every invocation and still refuses, as
does a request that supplies the real identifier of a page instance that has
already been rendered; a component the application disabled in
Component#onConfigure() is protected by neither, because that callback has not
run.
An application is affected where it withholds an individual component from the
caller, either by denying the RENDER action through IAuthorizationStrategy,
including through the MetaDataRoleAuthorizationStrategy and AuthorizeAction
facilities of wicket-auth-roles, or by setting the component's visibility or
enabled flag in Component#onConfigure(), the callback Wicket's own
documentation directs applications to use for both. The page carrying such a
component has to be constructible from a bookmarkable or mounted URL, which
requires a public constructor taking either no arguments or a PageParameters
argument. Behaviours pass through the same gate, so an AJAX behaviour attached
to such a component is equally exposed. Separately, and whether or not any
component is withheld, a listener on a page Wicket considers stateful is
invoked on an instance the request itself constructed, so it acts on models
built from page parameters the caller supplied rather than on the state the
application last rendered. Instantiation authorization is unaffected:
IAuthorizationStrategy#isInstantiationAuthorized() is still consulted when the
new page instance is created, so a guard placed on the page rather than on the
individual component continues to hold.
This issue affects Apache Wicket: from 8.0.0 through 8.19.0, from 9.0.0 through
9.24.0, from 10.0.0 through 10.11.0. Users are recommended to upgrade to
version 8.20.0, 9.25.0 or 10.12.0, which fix the issue.
Credit:
Emond Papegaaij (finder)
References:
https://wicket.apache.org/
https://www.cve.org/CVERecord?id=CVE-2026-82704