Apache Allura up to 1.19.0 client-side enforcement of server-side security

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
6.0$0-$5k1.89

Summaryinfo

A vulnerability classified as critical has been found in Apache Allura up to 1.19.0. This impacts an unknown function. This manipulation causes client-side enforcement of server-side security. This vulnerability is handled as CVE-2026-73239. The attack can be initiated remotely. There is not any exploit available.

Detailsinfo

A vulnerability has been found in Apache Allura up to 1.19.0 and classified as critical. Affected by this vulnerability is some unknown processing. The manipulation with an unknown input leads to a client-side enforcement of server-side security vulnerability. The CWE definition for the vulnerability is CWE-602. The product is composed of a server that relies on the client to implement a mechanism that is intended to protect the server. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:

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.

The advisory is shared at allura.apache.org. This vulnerability is known as CVE-2026-73239 since 08/11/2026. The exploitation appears to be easy. The attack can be launched remotely. Neither technical details nor an exploit are publicly available. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 08/12/2026).

Upgrading to version 1.19.1 eliminates this vulnerability.

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Vendor

Name

Version

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 6.3
VulDB Meta Temp Score: 6.0

VulDB Base Score: 6.3
VulDB Temp Score: 6.0
VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍

Exploitinginfo

Class: Client-side enforcement of server-side security
CWE: CWE-602
CAPEC: 🔒
ATT&CK: 🔒

Physical: No
Local: No
Remote: Yes

Availability: 🔒
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔒

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

0-Day Time: 🔒

Upgrade: Allura 1.19.1

Timelineinfo

08/11/2026 CVE reserved
08/12/2026 +1 days Advisory disclosed
08/12/2026 +0 days VulDB entry created
08/12/2026 +0 days VulDB entry last update

Sourcesinfo

Vendor: apache.org

Advisory: allura.apache.org
Status: Confirmed

CVE: CVE-2026-73239 (🔒)
GCVE (CVE): GCVE-0-2026-73239
GCVE (VulDB): GCVE-100-389101

Entryinfo

Created: 08/12/2026 19:21
Changes: 08/12/2026 19:21 (53)
Complete: 🔍
Cache ID: 216::103

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Do you want to use VulDB in your project?

Use the official API to access entries easily!