Skip to main content
Mallory
CriticalPublic exploitVulnerability

CVE-2020-11530: Blind SQL Injection in ChopSlider3 WordPress Plugin

Published May 8, 2020 · Updated 1 month ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS9.8Critical · v3.1
EPSS95.4%100th percentile
CISA KEVNoNot listed
In the wildReported500 exploitation records in Mallory
Vendor
Idangero
IdentifiersCVE-2020-11530CWE-89 · Improper Neutralization of Special…

A blind SQL injection vulnerability exists in the ChopSlider3 WordPress plugin (version 3), specifically in the 'chopslider/get_script/index.php' file. The vulnerability is due to unsanitized user input from the 'id' GET parameter being directly concatenated into an SQL query, allowing attackers to execute arbitrary SQL commands as the WordPress database user. The vulnerability can be exploited via crafted GET requests, including delay-based blind SQL injection techniques (e.g., using sleep(10)). The issue was reported to the vendor but no response or patch was provided at the time of public disclosure.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation allows an unauthenticated attacker to execute arbitrary SQL queries in the context of the WordPress database user. This can lead to unauthorized access to sensitive data, modification or deletion of database content, and potentially full compromise of the affected WordPress site depending on the database user's privileges.

Mitigation

If you can’t patch tonight, do this now.

As no official patch is available, immediate mitigation steps include removing or disabling the ChopSlider3 plugin. Additionally, restrict access to the vulnerable endpoint via web server configuration or a web application firewall (WAF) to block malicious requests exploiting the 'id' parameter.

Remediation

Patch, then assume compromise.

The recommended remediation is to update the vulnerable code to use prepared statements with parameterized queries for all database interactions involving user-supplied input. Site administrators should disable or remove the ChopSlider3 plugin until a patched version is available.

Public exploits

Exploits

No validated public exploits yet. Hidden: 1 rejected by Mallory's analysis as not a working exploit; 1 not yet analyzed, such as Exploit-DB entries.

View more in app →
Candidate exploits are awaiting analysis. View them in Mallory.
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
IdangeroChop Sliderapplication
FAQ

Frequently asked questions

Is CVE-2020-11530 exploited in the wild?
Yes. As of Oct 16, 2026, Mallory has reports of exploitation in the wild.
Is there a public exploit for CVE-2020-11530?
Yes. As of Oct 16, 2026, Mallory has reports of a public exploit for CVE-2020-11530.
Is there a patch for CVE-2020-11530?
The recommended remediation is to update the vulnerable code to use prepared statements with parameterized queries for all database interactions involving user-supplied input. Site administrators should disable or remove the ChopSlider3 plugin until a patched version is available.
What products are affected by CVE-2020-11530?
Idangero Chop Slider.
How severe is CVE-2020-11530?
CVE-2020-11530 has a CVSS v3.1 score of 9.8 (Critical) and an EPSS score of 95.4% (100th percentile) as of Oct 16, 2026.
Activity feed

Recent activity

No public activity tracked yet. Mallory keeps watching.

View more in app →

No public activity observed for this vulnerability.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signatures1YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activityCommunity discussion across Reddit, Mastodon, and other social sources.