Loading vulnerability…
DP Calendar versions 5.5.0 through 10.11.2 for Joomla contain an authenticated, privileged blind SQL injection vulnerability in its content-plugin functionality. Saving an article can cause attacker-controlled input to reach a database query unsafely when the DP Calendar content plugin is enabled. Exploitation requires an authenticated user with permission to update articles.
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 executable Python proof-of-concept, exploit/exploit.py. It targets a claimed SQL injection in DPCalendar Free's plg_content_dpcalendar shortcode handling: an attacker-controlled order attribute in an {{#events}} shortcode is asserted to reach an SQL ORDER BY clause without identifier validation. The script is an authenticated web exploit, not merely a detector. It establishes a requests session, obtains Joomla CSRF tokens, logs in with hardcoded Author credentials, creates a reusable draft article when possible, and repeatedly saves that article with a time-delay SQL payload. Response time at or above the configured 10-second SLEEP value is interpreted as a true condition. Three samples and majority voting are used for each test, then printable ASCII brute forcing reconstructs selected values. Its extraction targets are narrowly hardcoded to the first row of joomla.jos_users, so portability depends on the database/table prefix assumptions. README claims the issue affects DPCalendar Free through 10.11.2 and is fixed in 10.12.0; these version and CVE claims are repository assertions rather than independently verified by the included code.
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, 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.