Allura

allura

Vendor: Apache • 12 CVEs

CVEs (12)

CVE VENDORS PRODUCTS UPDATED PUBLISHED CVSS
CVE-2026-75099 1Apache 1Allura Aug 28, 2026 Aug 24, 2026 N/A· v4 5.3 MEDIUM· v3 N/A· v2 Unauthenticated REST disclosure of certain content items in Apache Allura. This issue affects Apache Allura: through 1.19.1. Users are recommended to upgrade to version 1.20.0, which fixes the issue.
CVE-2026-73240 1Apache 1Allura Aug 17, 2026 Aug 12, 2026 N/A· v4 9.8 CRITICAL· v3 N/A· v2 Specifically crafted inputs may lead to git argument injection in Apache Allura. This issue affects Apache Allura: before 1.19.1. Users are recommended to upgrade to version 1.19.1, which fixes the issue.
CVE-2026-73239 1Apache 1Allura Aug 17, 2026 Aug 12, 2026 N/A· v4 6.5 MEDIUM· v3 N/A· v2 Insecure Direct Object Reference (IDOR) due to missing permission checks for multiple Artifact types in Apache Allura. This issue affects Apache Allura: before 1.19.1. Users are recommended to upgrade to version 1.19.1...Show more Insecure Direct Object Reference (IDOR) due to missing permission checks for multiple Artifact types in Apache Allura. This issue affects Apache Allura: before 1.19.1. Users are recommended to upgrade to version 1.19.1, which fixes the issue.Show less
CVE-2026-73238 1Apache 1Allura Aug 17, 2026 Aug 12, 2026 N/A· v4 6.1 MEDIUM· v3 N/A· v2 XSS vulnerability in code display in Apache Allura. This issue affects Apache Allura: before 1.19.1. Users are recommended to upgrade to version 1.19.1, which fixes the issue.
CVE-2026-73237 1Apache 1Allura Aug 17, 2026 Aug 12, 2026 N/A· v4 6.1 MEDIUM· v3 N/A· v2 XSS vulnerability in Markdown handling in Apache Allura. This issue affects Apache Allura: from 1.10.0 before 1.19.1. Users are recommended to upgrade to version 1.19.1, which fixes the issue.
CVE-2026-69223 1Apache 1Allura Aug 17, 2026 Aug 11, 2026 N/A· v4 9.1 CRITICAL· v3 N/A· v2 Apache Allura's webhooks are vulnerable to Server-Side Request Forgery (SSRF). This issue affects Apache Allura: before 1.19.1. Users are recommended to upgrade to version 1.19.1, which fixes the issue.
CVE-2024-38379 1Apache 1Allura Jun 17, 2026 Jun 22, 2024 N/A· v4 4.8 MEDIUM· v3 N/A· v2 Apache Allura's neighborhood settings are vulnerable to a stored XSS attack. Only neighborhood admins can access these settings, so the scope of risk is limited to configurations where neighborhood admins are not fully...Show more Apache Allura's neighborhood settings are vulnerable to a stored XSS attack. Only neighborhood admins can access these settings, so the scope of risk is limited to configurations where neighborhood admins are not fully trusted. This issue affects Apache Allura: from 1.4.0 through 1.17.0. Users are recommended to upgrade to version 1.17.1, which fixes the issue. Show less
CVE-2024-36471 1Apache 1Allura Jun 17, 2026 Jun 10, 2024 N/A· v4 7.5 HIGH· v3 N/A· v2 Import functionality is vulnerable to DNS rebinding attacks between verification and processing of the URL. Project administrators can run these imports, which could cause Allura to read from internal services and expos...Show more Import functionality is vulnerable to DNS rebinding attacks between verification and processing of the URL. Project administrators can run these imports, which could cause Allura to read from internal services and expose them. This issue affects Apache Allura from 1.0.1 through 1.16.0. Users are recommended to upgrade to version 1.17.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. Show less
CVE-2023-46851 1Apache 1Allura Jun 17, 2026 Nov 7, 2023 N/A· v4 4.9 MEDIUM· v3 N/A· v2 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 in...Show more 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. Show less
CVE-2019-10085 1Apache 1Allura Jun 17, 2026 Jun 19, 2019 N/A· v4 6.1 MEDIUM· v3 4.3 MEDIUM· v2 In Apache Allura prior to 1.11.0, a vulnerability exists for stored XSS on the user dropdown selector when creating or editing tickets. The XSS executes when a user engages with that dropdown on that page.
CVE-2018-1319 1Apache 1Allura Nov 21, 2024 Mar 15, 2018 N/A· v4 6.1 MEDIUM· v3 4.3 MEDIUM· v2 In Apache Allura prior to 1.8.1, attackers may craft URLs that cause HTTP response splitting. If a victim goes to a maliciously crafted URL, unwanted results may occur including XSS or service denial for the victim's bro...Show more In Apache Allura prior to 1.8.1, attackers may craft URLs that cause HTTP response splitting. If a victim goes to a maliciously crafted URL, unwanted results may occur including XSS or service denial for the victim's browsing session.Show less
CVE-2018-1299 1Apache 1Allura Nov 21, 2024 Feb 6, 2018 N/A· v4 7.5 HIGH· v3 5.0 MEDIUM· v2 In Apache Allura before 1.8.0, unauthenticated attackers may retrieve arbitrary files through the Allura web application. Some webservers used with Allura, such as Nginx, Apache/mod_wsgi or paster may prevent the attack...Show more In Apache Allura before 1.8.0, unauthenticated attackers may retrieve arbitrary files through the Allura web application. Some webservers used with Allura, such as Nginx, Apache/mod_wsgi or paster may prevent the attack from succeeding. Others, such as gunicorn do not prevent it and leave Allura vulnerable.Show less