WPdeeply
30 published guides
miniOrange SAML Single Sign On – Unauthenticated Authentication Bypass Across Seven Editions
Two miniOrange SAML Single Sign On flaws can let unauthenticated attackers sign in as existing WordPress users, including administrators. Paid editions need manual version checks because the normal…
Elementor Pro <= 4.2.1 - Unauthenticated Arbitrary File Upload to RCE
Elementor Pro versions up to 4.2.1 contain a critical unauthenticated arbitrary file upload vulnerability in the Forms module. Update to 4.2.2 or later and inspect Elementor form upload…
Forminator Forms <= 1.56.1 - Unauthenticated Arbitrary File Upload
Forminator Forms versions up to 1.56.1 contain a critical unauthenticated arbitrary file upload vulnerability. Update to 1.56.2 or later and review public forms that combine Select and File…
Hello to Performances: Why Speed Is Part of WordPress Security
Performance is not separate from security. A slow WordPress site is easier to overwhelm, harder to monitor, and more likely to be running outdated plugins that nobody wants…
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…
WP Job Manager Permission Escalation to RCE: Risk Profile and Response
Permission escalation is dangerous because it changes who can perform sensitive actions. On a WordPress site, that can quickly become plugin installation, file writes, or code execution.
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.