Technical impact
Component templates in Apache Wicket can be inadvertently served as package resources when the framework’s class loader is isolated from the application’s class loader. The check that normally blocks such files relies on the presence of a class file with the same name; when wicket-core cannot see the application’s classes, the check fails and the template is delivered to the client. The disclosed content includes component structure, developer comments, conditional markup, inline scripts, and endpoint names, but does not expose user data or credentials. This vulnerability is identified as a CWE‑552 information exposure weakness.
Affected Systems
Apache Software Foundation’s Apache Wicket versions 8.0.0 through 8.19.0, 9.0.0 through 9.24.0, and 10.0.0 through 10.11.0 are affected. Versions prior to 7.x are unsupported and should be upgraded. Users of the affected releases are advised to update to 8.20.0, 9.25.0, or 10.12.0, which contain the fix.
Risk and Exploitability
The CVSS score of 6.3 indicates medium severity; the EPSS score is not available, suggesting limited evidence of active exploitation. The vulnerability is not listed in the CISA KEV catalog. Exploitation requires an attacker to know a component’s fully qualified class name, which is reflected in the URL for package resources. Because the supplied class loader configuration must isolate wicket-core from the application, many typical deployments are not affected, but certain shared or OSGi environments are vulnerable. If an attacker succeeds, they gain read‑only access to template files that may reveal application design or embedded scripts.