CVE-2023-23755 is an improper restriction of excessive authentication attempts in Joomla! versions 4.2.0 through 4.3.1. MFA methods lack rate limiting, allowing repeated brute-force attempts against those methods.
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 standalone Go-based Joomla credential attack toolkit named joombrute, not tied to a larger exploit framework. It is a real exploit repository with multiple offensive modules targeting Joomla 3/4/5 authentication and pre-auth disclosure weaknesses. The main CLI entry point is cmd/joombrute/main.go with Cobra-based subcommands defined under cmd/joombrute/*. Core logic is split into internal packages: internal/joomla handles target normalization, login form parsing, version detection, and login outcome classification; internal/brute implements concurrent admin login bruteforce with per-worker cookie jars and retry/backoff logic; internal/recon implements CVE-2023-23752 unauthenticated API harvesting; internal/mfa implements both CVE-2023-23755 TOTP brute force and CVE-2025-25227 MFA bypass probing; internal/httpx provides HTTP client/session/proxy plumbing; internal/output provides console and JSONL reporting. Primary capabilities: (1) detect fingerprints Joomla versions using /administrator/manifests/files/joomla.xml, frontend generator meta tags, and admin markup; (2) enum exploits CVE-2023-23752 against /api/index.php/v1/users?public=true and /api/index.php/v1/config/application?public=true to disclose usernames, DB credentials, SMTP credentials, and app secret; (3) brute performs concurrent credential attacks against /administrator/ using parsed CSRF token names and session cookies, classifying outcomes as success, invalid, blocked, or mfa-required; (4) mfa-brute exploits CVE-2023-23755 by exhausting 6-digit TOTP codes against the captive MFA validation flow; (5) mfa-bypass probes CVE-2025-25227 by replaying a half-authenticated session against bypass candidate com_users views/tasks such as view=methods; and (6) chain automates detect -> enum -> brute -> MFA bypass pivot. The exploit is operational rather than just a PoC because it includes working attack logic, concurrency controls, retry handling, proxy/TLS options, structured output, and an end-to-end chain mode. It does not deliver a traditional shell payload; instead, its payload is authenticated HTTP interaction intended to obtain admin access or disclose secrets. The repository also includes a full lab environment under lab/ with Docker Compose, installer scripts, MFA seeding PHP, and TOTP helper code for reproducible testing against Joomla 3.10, 4.2.7, and 5.x. Test fixtures and unit/integration tests under testdata/ and internal/*_test.go validate parsing and exploit behavior. Overall purpose: automate Joomla reconnaissance and credential/MFA attacks across multiple CVEs and versions, with emphasis on admin access acquisition and post-password MFA defeat.
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.
1 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.
No news coverage yet. Advisories and community discussion only.
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.