WordPress Vulnerability
15
Guides
WordPress Importer — Arbitrary Post Creation
The official WordPress Importer accepts a structured file and creates content from it. WPDeeply’s 2021 disclosure examined what happens when the file is not trustworthy.
WordPress $wpdb->prepare(), Denial of Service, and Memory Limits
The practical risk is not that every use of $wpdb->prepare() is dangerous. The risk is that database helper code can become a denial-of-service path when untrusted input creates…
Abandoned Cart Lite for WooCommerce before 5.8.2 — SQL Injection
Unsanitised cart parameters in Abandoned Cart Lite for WooCommerce exposed stored customer data to unauthenticated extraction. Fixed in 5.8.3.
Loginizer before 1.6.4 — Unauthenticated SQL Injection
An unauthenticated SQL injection in Loginizer’s brute-force protection, reachable from any WordPress login form. Fixed in 1.6.4 — and pushed to over a million sites by a rare…
Ninja Forms before 3.4.27.1 — Simple CSRF to RCE
A missing request-origin check in Ninja Forms let one crafted link, clicked by a logged-in administrator, escalate into code execution. Fixed in 3.4.27.1.
WooCommerce before 4.1.0 — Remote Code Execution
A security fix that reached millions of stores through a changelog line reading like routine maintenance — and the ecosystem of plugins that copied the original code.
WordPress Protected Meta Exposure via WP Job Manager: What Site Owners Should Know
Protected meta is only protected if every plugin respects the boundary. Job, listing, and directory plugins often attach sensitive operational data to posts, so permission checks matter.
WordPress Attachment API Functions and Any Post Type: The Hidden Risk
Attachment handling is security-sensitive because files, metadata, authorship, and post relationships meet in one place. Treat upload and attachment helpers as privileged code.
WordPress and PHAR Unserialize: Why File Handling Can Become Code Risk
PHAR unserialize risk is about file operations becoming object-deserialization triggers. If a plugin lets attackers influence file paths, normal-looking checks can become dangerous.
WordPress and Multiple maybe_unserialize Calls: When Data Parsing Gets Risky
Repeated unserialization is a smell. If user-influenced data is parsed again and again, developers should ask whether the application is normalizing data or accidentally expanding attacker control.