Loading story…
A file-read vulnerability in the Smart Slider 3 WordPress plugin could let authenticated users with only subscriber-level access read arbitrary files from the server, including wp-config.php, on more than 500,000 likely unpatched sites. The flaw, tracked as CVE-2026-3098, affects all versions through 3.5.1.33 and stems from missing capability checks and insufficient file validation in the plugin’s AJAX export functionality.
Researcher Dmitrii Ignatyev reported the issue, which was validated by Wordfence before developer Nextendweb released a fix in Smart Slider 3 3.5.1.34. Security reporting said there was no evidence of active exploitation at publication time, but successful attacks could expose database credentials, cryptographic keys, and WordPress salt values, creating a path to broader site compromise.
Mallory correlates global threat intelligence with your attack surface — know if you’re exposed before adversaries strike.
4 events from the most recent confirmed update back to the earliest known activity.
By March 29-30, public reporting disclosed CVE-2026-3098 and warned that although Smart Slider 3 is active on more than 800,000 sites, at least 500,000 WordPress sites likely remained vulnerable because they had not yet updated. Reports said there was no evidence of active exploitation at the time, but successful attacks could expose database credentials, cryptographic keys, and WordPress salts, enabling broader site compromise.
Security researcher Dmitrii Ignatyev discovered an arbitrary file-read vulnerability in the Smart Slider 3 WordPress plugin and reported it to Wordfence, which validated the issue and notified plugin developer Nextendweb. The flaw was later tracked as CVE-2026-3098 and affects versions through 3.5.1.33.
On March 24, Nextendweb released Smart Slider 3 version 3.5.1.34 to fix the authenticated arbitrary file-read vulnerability caused by missing capability checks and insufficient file validation in AJAX export functionality. The bug could allow subscriber-level users to read sensitive files such as wp-config.php.
On 2026-02-24, Wordfence rolled out firewall protections for paid users against the Smart Slider 3 arbitrary file-read flaw later tracked as CVE-2026-3098. The mitigation followed researcher Dmitrii Ignatyev's report through the Wordfence Bug Bounty Program on February 23.
Vulnerabilities, threat actors, malware, products, organizations, and breaches Mallory has linked to this story.
3 references tracked. Mallory keeps watching after this page renders.
cybersecuritynews.com
Open sourcescworld.com
Open sourcebleepingcomputer.com
Open sourceMap indicators from this story to your assets and identify affected systems in minutes.
Every observed campaign, victim, and pivot linked to actors named in this story.
Malware, exploits, and IOCs connected to the activity described here.
YARA, Sigma, and Snort rules deployed to your SIEM as soon as they’re published.
Get matching new stories delivered to your team as they break — not the next morning.
Ask questions about this story and take action on the answers.
Other stories Mallory is tracking that overlap on entities, sources, or topic labels.
A critical vulnerability in the **Smart Slider 3** WordPress plugin exposed more than **800,000 websites** to arbitrary file read attacks, allowing authenticated users to access sensitive files on affected servers. The flaw, tracked as **`CVE-2026-3098`** and rated **CVSS 6.5**, affects **version `3.5.1.33` and earlier** of the widely used plugin. Researchers said the issue stems from the plugin’s **`actionExportAll()`** function, which does not properly validate the format and source of requested files. That weakness lets even low-privileged users, including **subscribers**, read arbitrary files such as **`wp-config.php`**, creating a risk of credential theft and broader compromise. Defenders were urged to update immediately to **Smart Slider 3 `3.5.1.34` or later**.
Jul 24, 2026
Multiple **WordPress plugins** were flagged for severe vulnerabilities that could let attackers take over sites through unauthenticated file upload, SQL injection, arbitrary file deletion, and authorization bypass. References point to issues in plugins including **WP Duplicate**, **Ninja Forms File Upload**, **Ultimate Member**, **Product Addons for WooCommerce**, **CleanTalk Spam Protect**, **Ally**, **Perfmatters**, and **Kali Forms**, alongside identifiers such as **`CVE-2024-48930`**, **`CVE-2025-13192`**, and **`CVE-2026-1104`**. Several flaws were described as allowing arbitrary plugin installation, malicious file upload, or direct database manipulation, creating a path to remote code execution and full site compromise. Wordfence reports indicate the exposure spans **hundreds of thousands of WordPress sites**, with some bugs already under **active exploitation**. The most serious cases include an unauthenticated SQL injection flaw in the **Ally** plugin affecting roughly **400,000 sites**, an arbitrary file deletion issue in **Perfmatters** affecting about **200,000 sites**, and active attacks targeting a critical flaw in **Kali Forms**. Taken together, the disclosures show a broad wave of high-impact plugin security failures that increase the risk of website defacement, malware deployment, data theft, and administrator-level compromise across the WordPress ecosystem.
Jul 12, 2026
A critical vulnerability tracked as **CVE-2026-49777** was disclosed in ShapedPlugin's **Product Slider Pro for WooCommerce** WordPress plugin, with reports describing it as a **backdoor** and **supply-chain remote code execution** issue. The flaw was assigned **CWE-1284** and a **CVSS 3.1** score reflecting critical impact (`AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H`), indicating that attackers could potentially compromise confidentiality, integrity, and availability without authentication or user interaction. Public reporting shows inconsistent affected-version boundaries, with one source listing versions **before 3.5.3** and another identifying versions **before 3.5.4**, while a Nuclei template pull request labels the issue as **KEV** and ties it to active detection efforts. The CVE record also notes that the vendor said the issue was fixed in an existing release but did not clearly publish a definitive patched version, leaving defenders to verify plugin versions carefully and treat older deployments as potentially exposed until remediation guidance is clarified.
Jun 29, 2026