Loading vulnerability…
CVE-2026-67363 is a business logic flaw in Balbooa Forms for Joomla before version 2.4.3.2 affecting the payment-processing endpoints used for Stripe and Authorize.Net transactions. The vulnerable stripeCharges and payAuthorize endpoints accept the transaction total from a client-controlled request parameter and pass that value to the payment gateway without recalculating the amount from the server-side form configuration and product pricing. The endpoints also do not enforce authentication or CSRF protections. As a result, an unauthenticated attacker can submit crafted payment requests that alter the amount charged and manipulate purchase metadata such as line items, quantities, and shipping values.
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.
The repository contains a README and one standalone, standard-library-only Python 3 exploit program, `balbooa_forms_poc.py`. It targets two claimed pre-authentication issues in Balbooa Forms for Joomla before 2.4.3.2. For CVE-2026-67364, it first obtains an anonymously exposed CSRF token from `form.getSessionToken`, then probes or exploits `form.message` using an injected URL parameter that is described as being inserted unescaped into a custom PHP form handler and executed via `eval`. Detection sweeps configurable form and submit-button ID ranges with a marker payload; RCE mode executes a configurable command; shell mode is explicitly destructive and writes `images/shell.php`. For CVE-2026-67363, the script targets unauthenticated Stripe and Authorize.net payment actions and supplies a user-selected, client-controlled order total, with an explicit opt-in acknowledgement because it can trigger real payment attempts. The README additionally references a Nuclei detection template, but that YAML file is not present in the supplied two-file repository; therefore this is not analyzed as a Nuclei framework repository.
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.