CVE-2026-5073 is an unauthenticated SQL injection vulnerability in the ARMember Premium plugin for WordPress affecting all versions up to and including 7.3.1. The flaw is present in the arm_directory_paging_action AJAX action and is exploitable via the user-controlled order parameter, with supporting context indicating unsafe handling of both order and orderby inputs. The root cause is insufficient escaping of attacker-supplied parameters combined with inadequate preparation of the SQL statement in the arm_get_directory_members() function. This allows an unauthenticated attacker to append SQL fragments to an existing query and manipulate database operations to retrieve sensitive 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 (1 hidden).
This repository is a small standalone Python exploit for CVE-2026-5076 affecting the WordPress ARMember premium plugin, with the README documenting the vulnerability and main.py implementing the attack workflow. The code is not part of a larger exploit framework. The script uses requests, regex parsing, argparse, and ThreadPoolExecutor to support single-target or bulk-target exploitation. The exploit logic shown in the available code performs several stages: it first fingerprints a target WordPress site for ARMember by requesting the homepage and /wp-json/ and searching for ARMember-specific markers; it then attempts to discover a public member directory page by searching the site, trying common directory-related paths, and parsing /sitemap.xml; once found, it extracts arm_wp_nonce and template_id values from the page source. Based on the README and variable names present in the code (admin_login, admin_id, admin_email, arm_reset_key, wp_prefix), the remaining workflow is intended to recover an administrator identity and plaintext reset key, then reset the administrator password to an attacker-chosen value. The CLI defaults to a takeover password of Pwn3d_by_CVE20265076! and supports multithreaded scanning, verbose logging, configurable timeout, and writing successful results to exploited.txt. Repository structure is minimal: README.md contains vulnerability metadata, affected versions, impact, and remediation guidance; main.py is the operational exploit entry point. The exploit is clearly offensive rather than merely diagnostic, because its stated and coded purpose is to achieve unauthorized password reset and account takeover, not just detect exposure.
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.
7 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
Referenced only as a methodological lesson for a coverage guard filter; no substantive vulnerability details are provided in the content.
An unauthenticated SQL injection vulnerability affecting WordPress ARMember Premium versions 7.3.1 and earlier.
A referenced vulnerability that can be combined with CVE-2026-5076 to extract plaintext reset keys and enable account takeover; described only as SQL injection in this content.
An unauthenticated SQL injection vulnerability in ARMember Premium via the order parameter, usable to extract database contents and chain into admin takeover with CVE-2026-5076.
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.