Skip to main content
VulnerabilityPublished

CVE-2026-3020: Wakyma application web · Insecure Direct Object Reference

Affects Wakyma application webSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 8.6 High.

Data as of 30 Oct 2026, 11:52 UTC

CVSS 4.0 base score
8.6High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 13% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 16 Mar 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
WakymaWakyma application webAffected
  • =all versions
Fixed in–

AI-suggested

To mitigate CVE-2026-3020, organizations should immediately implement strict authorization checks on all endpoints that allow modification of user account data. This includes validating that the authenticated user is authorized to perform changes on the targeted account and ensuring that user-controlled keys cannot be manipulated to reference other users' data. Employ robust access control mechanisms such as role-based access control (RBAC) or attribute-based access control (ABAC) to enforce least privilege principles. Monitor and log all account modification requests for unusual activity, and implement anomaly detection to identify potential abuse. Enforce multi-factor authentication (MFA) to reduce the impact of account takeover. Until official patches are released, consider applying web application firewalls (WAFs) with custom rules to detect and block suspicious requests targeting account modification endpoints. Conduct thorough code reviews and penetration testing focused on authorization logic to identify and remediate similar flaws. Educate users about phishing and social engineering risks that could compound this vulnerability.

Description

Identity based authorization bypass vulnerability (IDOR) that allows an attacker to modify the data of a legitimate user account, such as changing the victim's email address, validating the new email address, and requesting a new password. This could allow them to take complete control of other users' legitimate accounts

References

Community reviews

Loading reviews…