CVE-2023-46851CWE-20CWE-200CWE-73

CVE-2023-46851: vulnerability in Apache Allura

Apache Allura: sensitive information exposure via import

Published · Updated

Follow this CVE+ Monitor Apache Allura

E-mail alert when it lands in KEV, gets a public PoC or its score goes up.

3Vexday Risk Score

No sign of exploitation. No public exploitation artifact known so far.

ssvc Trackepss 1.6%
Allura Discussion and Allura Forum importing does not restrict URL values specified in attachments. Project administrators can run these imports, which could cause Allura to read local files and expose them.  Exposing internal files then can lead to other exploits, like session hijacking, or remote code execution. This issue affects Apache Allura from 1.0.1 through 1.15.0. Users are recommended to upgrade to version 1.16.0, which fixes the issue.  If you are unable to upgrade, set "disable_entry_points.allura.importers = forge-tracker, forge-discussion" in your .ini config file.
Affected products
Apache Software Foundation · Apache Allura
Related CVEs — Apache Allura

In the same product, most dangerous first.

CVE-2018-1299—CVE-2018-1299EPSS 3.0%CVE-2018-1319—CVE-2018-1319EPSS 2.2%CVE-2026-73240CRITICALApache Allura: Git command injectionEPSS 1.0%CVE-2026-73237MEDIUMApache Allura: XSS in markdown pipelineEPSS 0.8%CVE-2026-73238MEDIUMApache Allura: XSS in code displayEPSS 0.8%CVE-2026-69223CRITICALApache Allura: Server-side request forgeryEPSS 0.8%