CVE-2026-82557

Apache Wicket: A disabled or invisible form submitting component is still invoked on a plain form submission

Published Nov 1, 2026 CVSS 4.0 · 6.9 Medium EPSS < 1% KEV · Not listed
Description
Missing authorization in Apache Wicket.

org.apache.wicket.markup.html.form.Form resolves the component that submitted a form from the request parameters in Form#onRequest() and passes the result directly to Form#onFormSubmitted(IFormSubmitter). The check that the submitting component is visible and enabled in its hierarchy runs only when onFormSubmitted() is given no submitter, so it no longer runs for an ordinary form submission, and it is the only point at which Wicket verifies that the application actually offered the named control to the caller. Form#findSubmitter() matches on the request parameter name alone and applies no visibility or enablement filter, and the request handler checks only the form itself, which is visible and enabled. A request that names a submit button the application withheld therefore reaches that button's onSubmit() and onAfterSubmit(), and its onError() when form validation fails; where the button sets setDefaultFormProcessing(false) it reaches onSubmit() and onAfterSubmit() without any form validation.

An application is affected where a form submitting component, such as a Button or a SubmitLink, is unavailable to the caller while the enclosing form remains available. How the component was made unavailable does not matter: the component's own setVisible(false), setEnabled(false) or setVisibilityAllowed(false), an overridden isVisible() or isEnabled(), an invisible or disabled parent container anywhere above it, and a RENDER or ENABLE denial from IAuthorizationStrategy — for example through MetaDataRoleAuthorizationStrategy or the AuthorizeAction annotation — are all enforced by that one check, and all of them are bypassed. A component that renders as disabled carries its own input name in the markup the caller already holds. Submissions made through AjaxFormSubmitBehavior, and therefore through AjaxButton and AjaxSubmitLink, are not affected: those are invoked as a behaviour on the button itself, the behaviour's invocation is authorized against that button, and the non-Ajax callbacks of those two classes do nothing. Restrictions applied to the form or to the page rather than to the submitting component are unaffected.

The 9.x and 8.x release lines, and the unsupported lines before them, are not affected; the behaviour was introduced in 10.3.0.

This issue affects Apache Wicket: from 10.3.0 through 10.11.0. Users are recommended to upgrade to version 10.12.0, which fixes the issue.

Analysis

AI-generated

Technical impact

Apache Wicket allows an attacker to invoke the onSubmit logic of hidden or disabled form submit components, bypassing the visibility and enablement checks that normally prevent such components from being triggered. This flaw permits unintended execution of server‑side actions that the user should not be able to access, potentially causing unauthorized state changes or manipulation of sensitive data.

Affected Systems

The vulnerability affects Apache Wicket releases 10.3.0 through 10.11.0 inclusive. Versions 10.12.0 and later are not impacted, as are the earlier 8.x and 9.x lines. Any application built on these affected releases is at risk if it contains form submit components that become invisible or disabled via setVisible(false), setEnabled(false), or through authorization strategies that hide the component.

Risk and Exploitability

With a CVSS score of 6.9 the flaw is rated medium severity. The EPSS score is not available and the vulnerability is not listed in the CISA KEV catalog. Attackers can exploit this remotely by sending a crafted HTTP request that includes the name of a hidden or disabled submit button, without needing authentication beyond normal form access. The attacker can then trigger the associated onSubmit, onAfterSubmit, or onError methods, potentially causing unauthorized actions. The lack of visibility enforcement makes exploitation straightforward once the component is referenced.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade Apache Wicket to version 10.12.0 or later, which removes the flawed visibility check.
  • If an upgrade cannot be performed immediately, remove or rename any disabled or invisible submit components so that they do not appear in the form markup.
  • Add server‑side validation that rejects submissions that reference components that are disabled, invisible, or otherwise suppressed by authorization policies.
  • Conduct a security review of all forms in the application to verify that no critical actions are bound to disabled or invisible submit components and enable logging of unexpected submission events.

Generated by OpenCVE AI on November 1, 2026 at 23:51 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'yes', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
First Time appeared Apache
Apache wicket
Vendors & Products Apache
Apache wicket
Type Values Removed Values Added
Description Missing authorization in Apache Wicket. org.apache.wicket.markup.html.form.Form resolves the component that submitted a form from the request parameters in Form#onRequest() and passes the result directly to Form#onFormSubmitted(IFormSubmitter). The check that the submitting component is visible and enabled in its hierarchy runs only when onFormSubmitted() is given no submitter, so it no longer runs for an ordinary form submission, and it is the only point at which Wicket verifies that the application actually offered the named control to the caller. Form#findSubmitter() matches on the request parameter name alone and applies no visibility or enablement filter, and the request handler checks only the form itself, which is visible and enabled. A request that names a submit button the application withheld therefore reaches that button's onSubmit() and onAfterSubmit(), and its onError() when form validation fails; where the button sets setDefaultFormProcessing(false) it reaches onSubmit() and onAfterSubmit() without any form validation. An application is affected where a form submitting component, such as a Button or a SubmitLink, is unavailable to the caller while the enclosing form remains available. How the component was made unavailable does not matter: the component's own setVisible(false), setEnabled(false) or setVisibilityAllowed(false), an overridden isVisible() or isEnabled(), an invisible or disabled parent container anywhere above it, and a RENDER or ENABLE denial from IAuthorizationStrategy — for example through MetaDataRoleAuthorizationStrategy or the AuthorizeAction annotation — are all enforced by that one check, and all of them are bypassed. A component that renders as disabled carries its own input name in the markup the caller already holds. Submissions made through AjaxFormSubmitBehavior, and therefore through AjaxButton and AjaxSubmitLink, are not affected: those are invoked as a behaviour on the button itself, the behaviour's invocation is authorized against that button, and the non-Ajax callbacks of those two classes do nothing. Restrictions applied to the form or to the page rather than to the submitting component are unaffected. The 9.x and 8.x release lines, and the unsupported lines before them, are not affected; the behaviour was introduced in 10.3.0. This issue affects Apache Wicket: from 10.3.0 through 10.11.0. Users are recommended to upgrade to version 10.12.0, which fixes the issue.
Title Apache Wicket: A disabled or invisible form submitting component is still invoked on a plain form submission
Weaknesses CWE-862
References
Metrics cvssV4_0

{'score': 6.9, 'vector': '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'}

Weaknesses

Sources

Status
PUBLISHED
Assigner
apache
Published
Updated
Nov 6, 2026, 2:46 PM
Reserved
Aug 29, 2026, 7:13 PM
Status
Deferred
Published
Nov 1, 2026, 10:17 PM
Modified
Nov 6, 2026, 3:17 PM