Loading vulnerability…
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in kendysond Payment Forms for Paystack payment-forms-for-paystack allows SQL Injection.This issue affects Payment Forms for Paystack: from n/a through <= 4.0.1.
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.
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos.
This repository contains a proof-of-concept (PoC) exploit for CVE-2025-22652, a time-based blind SQL injection vulnerability in the Payment Forms for Paystack WordPress plugin (versions 4.0.1 and below). The exploit requires administrator credentials and targets the 'order' parameter in the admin submissions page of the plugin. The repository consists of a detailed README.md explaining the vulnerability, exploitation steps, and a Python script (poc.py) that automates the attack. The script logs in as an administrator, creates a Paystack form, and then uses time-based SQL injection payloads to extract the database name by measuring response delays. The main attack vector is through the WordPress admin interface, specifically the endpoint '/wp-admin/edit.php' with crafted parameters. The code is a functional PoC and does not weaponize the exploit beyond extracting the database name.
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.