Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2026-30954: CWE-639: Authorization Bypass Through User-Controlled Key in Kovah LinkAce

0
Medium
VulnerabilityCVE-2026-30954cvecve-2026-30954cwe-639
Published: Tue Mar 10 2026 (03/10/2026, 20:40:31 UTC)
Source: CVE Database V5
Vendor/Project: Kovah
Product: LinkAce

Description

LinkAce is a self-hosted archive to collect website links. In 2.1.0 and earlier, the processTaxonomy() method in LinkRepository.php allows authenticated users to attach other users' private tags and lists to their own links by passing integer IDs.

AI-Powered Analysis

AILast updated: 03/10/2026, 21:16:01 UTC

Technical Analysis

CVE-2026-30954 is an authorization bypass vulnerability identified in Kovah's LinkAce, a self-hosted link archiving application. The vulnerability affects versions 2.1.0 and earlier. The root cause lies in the processTaxonomy() method within LinkRepository.php, which processes taxonomy-related data such as tags and lists associated with links. This method improperly authorizes user input, specifically integer IDs that reference tags and lists. Authenticated users can exploit this flaw by supplying IDs corresponding to other users' private tags and lists, thereby attaching these private elements to their own links without proper permission. This results in unauthorized access and potential data leakage or manipulation of private user content. The vulnerability is classified under CWE-639 (Authorization Bypass Through User-Controlled Key), indicating that the application fails to correctly validate user privileges when processing keys or identifiers controlled by the user. The CVSS v4.0 base score is 5.3 (medium severity), reflecting that the attack vector is network-based, requires low complexity, no user interaction, and low privileges (authenticated user). The impact is limited to confidentiality and integrity of private tags and lists but does not affect availability or system-wide integrity. No public exploits or patches are currently available, so organizations must be vigilant in monitoring and applying fixes once released.

Potential Impact

The primary impact of CVE-2026-30954 is unauthorized access and modification of private user data within LinkAce instances. Attackers with valid credentials can manipulate the application to gain access to other users' private tags and lists, potentially leading to data leakage, privacy violations, and unauthorized data manipulation. This could undermine user trust and violate data protection policies, especially in environments where link archives contain sensitive or proprietary information. While the vulnerability does not allow full system compromise or denial of service, the breach of confidentiality and integrity of user data can have significant reputational and compliance consequences. Organizations relying on LinkAce for collaborative link management or archival must consider the risk of insider threats or compromised accounts exploiting this flaw. The medium severity score reflects the moderate risk, given that exploitation requires authentication but no additional user interaction or elevated privileges.

Mitigation Recommendations

To mitigate CVE-2026-30954, organizations should first verify if they are running LinkAce version 2.1.0 or earlier and plan to upgrade to a patched version once available. In the absence of an official patch, administrators can implement the following measures: 1) Restrict access to LinkAce instances to trusted users only, minimizing the risk of malicious authenticated users. 2) Review and harden authorization logic in the processTaxonomy() method by enforcing strict ownership checks on tags and lists before allowing modifications. 3) Implement application-layer monitoring and logging to detect unusual activity involving tag and list modifications. 4) Employ network segmentation and access controls to limit exposure of the LinkAce service. 5) Educate users about the importance of strong authentication and monitoring for suspicious account activity. 6) Consider deploying Web Application Firewalls (WAFs) with custom rules to detect and block suspicious requests manipulating taxonomy IDs. These targeted mitigations go beyond generic advice by focusing on the specific authorization bypass vector and operational controls to reduce risk until an official patch is released.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Data Version
5.2
Assigner Short Name
GitHub_M
Date Reserved
2026-03-07T17:34:39.981Z
Cvss Version
4.0
State
PUBLISHED

Threat ID: 69b0864a2f860ef943bb990f

Added to database: 3/10/2026, 8:59:54 PM

Last enriched: 3/10/2026, 9:16:01 PM

Last updated: 3/13/2026, 8:32:23 PM

Views: 15

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console in Console -> Billing for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses