CVE-2026-43975: Apache Wicket: Possible malicious path traversal in FolderUploadsFileManager
FolderUploadsFileManager in Apache Wicket does not validate or sanitize the uploadFieldId parameter or the clientFileName before constructing file paths, allowing an unauthenticated attacker to write arbitrary files outside the intended upload directory or read files from arbitrary locations on the server.
This issue affects Apache Wicket: from 8.0.0 through 8.17.0, from 9.0.0 through 9.22.0, from 10.0.0 through 10.8.0.
Users are recommended to upgrade to version 10.9.0, which fixes the issue.
Affected Software
Remediation
Patch Available
Event History
Frequently Asked Questions
What is the severity of CVE-2026-43975?
CVE-2026-43975 has been classified with a moderate severity level due to the potential for path traversal and arbitrary file writing.
How do I fix CVE-2026-43975?
To fix CVE-2026-43975, update Apache Wicket to the latest version that addresses the path traversal vulnerability.
Which versions of Apache Wicket are affected by CVE-2026-43975?
CVE-2026-43975 affects Apache Wicket versions from 8.0.0 to 8.17.0, 9.0.0 to 9.22.0, and 10.0.0 to 10.8.0.
Can an unauthenticated user exploit CVE-2026-43975?
Yes, CVE-2026-43975 allows an unauthenticated attacker to exploit the vulnerability by crafting malicious file uploads.
What should I do if I cannot immediately update due to CVE-2026-43975?
If immediate updating is not possible for CVE-2026-43975, consider implementing validation and sanitization of file inputs as a temporary mitigation.