GitLab CE and EE contain an improper authorization vulnerability affecting all versions from 18.9.1 before 18.9.7, 18.10 before 18.10.6, and 18.11 before 18.11.3. The flaw stems from insufficient authorization checks when handling access to confidential issue content in public projects. As a result, an authenticated user could access confidential issue content without having the intended permissions to view that information.
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 is a small standalone Python exploit for CVE-2025-4524, described as a local file inclusion vulnerability in the WordPress Madara Theme before 2.2.2.1. The repository contains only two files: a minimal README and a single executable script, WPMadara.py. The script is a multithreaded mass-checker/exploit. It reads a user-supplied target list, normalizes each entry to remove any scheme, then tries both HTTPS and HTTP connectivity for each host. For reachable targets, it sends a POST request to the WordPress AJAX endpoint /wp-admin/admin-ajax.php using the action madara_load_more and a directory traversal payload in the template parameter pointing to /etc/passwd. A successful exploit is determined by the presence of the string root:x:0:0 in the response body. Core capabilities: - Bulk scanning of many targets from a file. - Automatic HTTP/HTTPS selection per target. - Use of multiple threads for faster exploitation attempts. - Basic request header randomization via a small User-Agent list. - Writes confirmed vulnerable targets to vuln.txt. Repository structure and code flow: - README.md: brief vulnerability label and image link. - WPMadara.py: - configure(): prompts for thread count and target file. - normalize_base(): strips schemes and trailing slashes from targets. - banner()/Madara(): cosmetic terminal banner output. - create_stealth_session(): creates a requests session with SSL verification disabled and randomized User-Agent headers. - save_result(): appends findings to vuln.txt. - exploit_madara_lfi(): sends the actual exploit POST request and checks for /etc/passwd disclosure. - worker_logic(): per-thread worker that tests connectivity and launches exploitation. - core_engine(): queues targets and starts worker threads. - main block: loads targets from file and runs the scan. This is a real exploit rather than a pure detector because it actively attempts file disclosure using a concrete traversal payload. However, its payload is fixed to reading /etc/passwd and does not provide post-exploitation or arbitrary payload customization, so OPERATIONAL is the best fit.
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.
2 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
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.