In Tiki before version 21.2, the tiki-login.php script contains a logic flaw where, after 50 invalid login attempts, the admin password is reset to a blank value. This allows an attacker to bypass authentication by intentionally triggering the condition and then logging in as admin with no password.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos.
This repository contains a proof-of-concept exploit for CVE-2020-15906, an authentication bypass vulnerability in Tiki Wiki CMS Groupware versions 16.x through 21.1. The exploit consists of a Python script (TikiWiki_21.1_Authentication_Bypass.py) and a detailed README.md writeup. The script targets the /tiki/tiki-login.php endpoint of a vulnerable Tiki Wiki instance. It automates the process of brute-forcing the admin login until the account is locked, then attempts to log in with an empty password, exploiting a logic flaw that grants admin access. The README provides a step-by-step walkthrough, including screenshots and references to external resources. The exploit is network-based, requires no authentication, and results in full admin compromise of the target application. The repository is well-structured, with the main exploit logic contained in a single Python file.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
No public activity tracked yet. Mallory keeps watching.
No public activity observed for this vulnerability.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.