CVE-2026-83539 in Wicket
الملخص
بحسب VulDB • 02/11/2026
ضعف في التعقيم غير السليم للإدخال أثناء توليد صفحات الويب في Apache Wicket.
تقوم المكونات `org.apache.wicket.extensions.markup.html.basic.SmartLinkLabel` و `org.apache.wicket.extensions.markup.html.basic.SmartLinkMultiLineLabel` بعرض قيمة نصية وتحويل أي عنوان URL يتم العثور عليه فيها إلى رابط تشعبي (hyperlink). وكلاهما يفلتان القيمة النموذجية (model value) ثم يسلمان النص المُهمل إلى `org.apache.wicket.extensions.markup.html.basic.DefaultLinkParser`، الذي يبحث فيه عن أي شيء على شكل `scheme://rest` ويحيط بكل تطابق بوسم anchor whose href is the matched text, copied in as it is. The pattern accepts any scheme, and there is no list of permitted schemes anywhere on the path. A text value naming a scheme that executes script therefore becomes an anchor that executes it, in the application's origin and in the reader's own session, when the reader clicks the link. Rendering the page is not enough on its own; the link has to be activated. Escaping does not prevent this and is not the issue: the characters the payload needs are all valid in a URL and are ones that org.apache.wicket.util.string.Strings#escapeMarkup() leaves alone, and the value ends up in a URL rather than in element text, which is a context that escaping model data does not make safe.
An application is affected where it renders text it received through either of these two components. That is what they are for: they exist to linkify email addresses and web URLs found in the data an application is displaying, so untrusted input is the purpose of the feature rather than a misuse of it, and no unusual configuration is involved. No other component uses this parser, and an application that uses neither SmartLinkLabel nor SmartLinkMultiLineLabel is not affected.
On 9.x and 10.x the Content-Security-Policy Wicket sends by default admits script only from a source carrying a per-response nonce, and a URL whose scheme executes script cannot carry one, so that default policy stops the script from running. This is a property of the default policy and not of these components. An application that has weakened or disabled its Content-Security-Policy, for this or for any unrelated reason, is affected in full. Wicket 8.x has no Content-Security-Policy support at all and is affected as it stands.
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 of Apache Wicket 7.x or older, which are no longer supported, should upgrade to a supported version. Users are recommended to upgrade to version 8.20.0, 9.25.0 or 10.12.0, which fix the issue.
If you want to get best quality of vulnerability data, you may have to visit VulDB.