CVE-2026-111824 · Other
NO FIX YET · SEE WHAT TO DO
An author on a weblog using a custom theme can upload a file whose served type lets it run script when anyone opens its resource URL. That script runs in the browser of every visitor who opens the file, which is cross-site scripting.
first public Nov 11, 2026 · 1 source
Could this affect your app?
Free first check from your website. Connect your repo for the full answer.
Only Apache Roller 6.1.6 installations where media uploads are enabled and weblogs use custom themes are exposed. The attacker needs an Author account on such a weblog, and the risk is to visitors who open the uploaded file. Installations with media uploads disabled, the default, are not described as affected by the sources.
Not affected if default-config, media-uploads-disabled, no-custom-theme
Who cares apache-roller, java, self-hosted
roller package version; affected is 6.1.6.6.1.7 or later, as the sources recommend.Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') in Apache Roller 6.1.6 allows an authenticated user with the Author role on a weblog that uses a custom theme to store script that runs in the browser of anyone who opens the file's resource URL. The fix for CVE-2026-82387 serves uploaded media as a download unless it is an image, audio, video, PDF or plain text, but media files found through a custom theme were served with the type their path implies, and the upload form let the uploader choose that path. Media uploads are disabled by default. Users are recommended to upgrade to Apache Roller 6.1.7 or later, which serves these files under the same rules as other media and no longer accepts the path from the upload form.
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.
Check it with your coding agent
It reads this page and tells you if your code is affected.
Are you affected?
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.