Free tool: WordPress Plugin Vulnerability Checker
Look up any WordPress plugin: its current version from wordpress.org, and the known vulnerabilities our scanner checks for — in plain English, no scan required.
Plain-English security write-ups for AI builders: what vibe-coded apps typically expose, and how to check yours before you ship.
Look up any WordPress plugin: its current version from wordpress.org, and the known vulnerabilities our scanner checks for — in plain English, no scan required.
Check your own app — free, in about a minute.
The free mini-scan checks your live homepage for TLS/HTTPS basics, response security headers, cookie flags, exposed sensitive files, Firebase/Supabase backend rules, and the WordPress plugin versions your site exposes. You get a score and the finding titles — no account, no card.
Run the free mini-scan →AI coding tools ship working software, not secure software. The 7 vulnerabilities that show up most in vibe-coded apps — and how to check each before launch.
Don't ship your AI-built app without this checklist: auth, secrets, input handling, APIs, infrastructure. 25 practical security checks for vibe coders.
Why do AI-generated apps keep shipping the same vulnerabilities? An educational walkthrough of 5 recurring security patterns in vibe-coded apps.
Lovable itself isn't insecure — but the apps it generates ship with a predictable set of holes. What Lovable apps typically expose, how to verify each one, and what to fix before anyone else finds it.
Bolt generates working apps, not secure ones. What Bolt.new apps typically expose in the wild, how to check each one in minutes, and what to fix before you ship.
Replit is the fastest path from prompt to public URL — and its defaults are built for frictionless building, not security. What Replit-deployed apps typically expose and how to check yours.
"It renders beautifully" and "it's safe to put on the internet" are different statements. What v0-generated Next.js apps typically get wrong, and how to verify yours before you ship.
A step-by-step hardening guide for the standard Lovable stack (Lovable frontend + Supabase backend). Work through it in order; budget an afternoon.
Study after study finds 30–40% of AI-generated code contains vulnerabilities. Why the models get security wrong — and the vulnerability categories it produces.
The fastest meaningful security check you can run before shipping: ten minutes, a terminal, and curl. Catches the exposures behind the overwhelming majority of real-world incidents in AI-generated apps.
Generate ten apps with ten different tools and you'll find the same holes in most of them. The seven security mistakes that show up again and again, with concrete ways to find and fix each one.
The 24-point pre-deploy security checklist for Lovable apps: Row Level Security, secrets, Edge Function auth, headers, and launch hygiene — each with a concrete verification step.
API keys baked into JS bundles, committed to git, and loose service role keys — the five ways secrets leak in Bolt.new apps, with the exact commands to check each one.
Vercel handles TLS and the edge — the application layer is yours. What to verify in a v0-generated Next.js app: route auth, NEXT_PUBLIC_ secrets, headers, and preview deployments.
Replit Agent ships a working app at a public URL — locking it down is a separate pass. Secrets, unauthenticated endpoints, database access, and the 8-check lockdown pass.
No AI builder ships secure apps by default. An honest, checkable comparison of where Lovable, Bolt.new, v0, and Replit Agent apps typically leak — and what to verify on each before shipping.
Something feels off about your app? The real-world signs of compromise — injected spam, unknown accounts, unexpected charges — how to check each, and what to do in the first hour.
The six security headers a real scan checks — HSTS, CSP, X-Frame-Options, X-Content-Type-Options, Referrer-Policy, Permissions-Policy — what each does, and how to verify yours in two minutes with curl.
Three tiny flags decide whether your cookies survive the two most common web attacks. What Secure, HttpOnly, and SameSite do, how to audit yours in DevTools, and why AI-generated apps keep shipping without them.
Two curl commands that catch one of the highest-severity exposures in AI-deployed apps: a publicly reachable .env or .git directory. Why it happens, how to fix it, and what to rotate if it was exposed.
Xcode projects leak secrets in predictable places: .xcconfig files, hardcoded keys in Swift, GoogleService-Info.plist, ATS overrides, and git history. The pre-submission checklist for each one.
One boolean in Info.plist turns off iOS's HTTPS enforcement for your whole app. What ATS actually enforces, what each exception key does, and how to scope an exception to the one domain that needs it.
Before you add that library or fork that starter: committed secrets, vulnerable dependencies, and hygiene red flags. The repeatable pass — by hand, or automated — for any repo you're about to trust.
Social login done wrong is an account-takeover feature. Server-side token verification, linking accounts by verified email only, state parameters, and Apple's one-time name — the parts builders skip.
Package.resolved is the exact list of third-party code your app ships — including transitive packages you never chose. How to read it, check pins against known vulnerabilities, and spot the pins that can't be checked.
A timed workflow for ship day: free mini-scan, full scan with evidence, fix in priority order, rescan to prove it, then monitoring so the next deploy doesn't reopen everything.
CVE-2026-109618 and CVE-2026-109619 — two unauthenticated remote-code-execution flaws in PHP core, CVSS 9.2 each, exploited in the wild — were patched on October 21, 2026. The fixed versions, the 60-second version check, and why PHP 8.1 and older get no fix at all.
CVE-2026-115806 — a CVSS 9.8 unauthenticated PHP object-injection flaw in the Prime Mover WordPress backup plugin (10,000+ installs). A crafted comment can plant a payload that fires on a later export or restore. Affected versions, the vendor-vs-Wordfence patch dispute, and what to do now.
CVE-2026-116163 — a CVSS 9.1 authentication bypass in Parse Server: custom auth adapters subclassing AuthAdapter never had their validation methods called, so any authData was accepted. Affected versions (< 8.6.102 / < 9.10.5), the narrow scope (built-in and plain-object adapters are NOT affected), and what to do now.
CVE-2026-82814 — an unauthenticated PHP object injection flaw in the Duplicator WordPress backup plugin (1M+ installs). The payload is planted by a visitor and fires later, when an admin runs a migration. Affected versions, the 5.0.0 fix, and why you should not run a migration before updating.
CVE-2026-94267 — ACF Extended's front-end form post-update action runs without a capability check, so an unauthenticated visitor can overwrite arbitrary posts where a published form maps its target and content to submitted values. The precondition, stated straight, and the 0.9.2.8 fix.
The critical WordPress disclosures that landed under the php2shell headlines: Newsletters SQL injection + object injection (CVE-2026-111402 / CVE-2026-94075), Product Filter by WBW blind SQLi (CVE-2026-112866), Paytium object injection (CVE-2026-114196), aBlocks privilege escalation (CVE-2026-110018), the unpatched Helion theme (CVE-2026-112852), and the asVereinbase auth bypass (CVE-2026-110956) — versions and fixes.
CVE-2026-114509 — Laravel's built-in TokenGuard mishandles a crafted non-string credential under MySQL/MariaDB, authenticating an attacker as an existing user without their token. Affected (< 12.68.0 / 13.x < 13.29.0), fixed in 12.68.0 / 13.29.0, and the server-side check — no outside scanner can see your framework version.
On October 21, 2026, LiteLLM's release pipeline was hijacked and malicious litellm==1.107.0 artifacts — credential-stealing malware — shipped through PyPI, Docker Hub, and GHCR for about two hours. The official timeline, the vendor's remediation (delete, rebuild, rotate everything), and the pinning habits that contain the next one.
CVE-2026-111497 — an out-of-bounds write in the Brotli decoder bundled with Node.js: a malformed stream is treated as 'need more input' while the decoder keeps appending to an 8-byte buffer. Affected 22/24/26 lines, fixed in 26.12.1 / 24.22.1 / 22.23.4, and why runtime versions belong on your patch list next to packages.
CVE-2026-106013 — Jupiter X Core's Twitter/X social login never swaps in the visitor's token, so verify_credentials returns the site operator's profile and the plugin logs the visitor in as that account, typically the admin. Affected ≤ 4.61.0; the CVE record names no patched version yet — disable the X login.
CVE-2026-75891 — Kirki's kirki_post_apis() AJAX dispatcher deserializes untrusted input in its get-single-symbol branch with no capability check, so any Subscriber-level account can inject a PHP object; with a POP chain present, an administrator's password can be overwritten. Affected ≤ 6.2.5; fixed in 6.3.0.
CVE-2026-92885 — a misspelled variable in Qode Membership's Facebook token-verification guard makes the check always pass, so the social-login routine logs in any supplied account name — Administrators included — with no credential or token validation. The plugin ships bundled with Qode's Bridge theme. Affected ≤ 2.0.6.2; fixed in 2.0.6.3.
WordPress 7.1.4 patches a race condition in the Core update process: for the seconds a full-package update is unpacking, a staged copy of WordPress — installer included — sits in a predictable web-accessible directory, and an unauthenticated attacker who requests it in that window can reach remote code execution (Wordfence CVSS 8.1; no CVE assigned yet). Affected Core 4.7–7.1.3, patched per branch in the 7.1.4 line. Wordfence logged 18,500+ exploitation attempts in the first 21 hours — verify the patch actually landed on your site.
CVE-2026-84999 — Pie Register Premium's file-upload function runs WordPress's file-type validation and never checks the result before saving the file, and its AJAX handler has no nonce or capability check, so an unauthenticated visitor can upload a PHP file and execute it. Affected Premium ≤ 3.8.4.0; the CVE record names NO patched version yet — disable the plugin or its upload fields. Not the free Pie Register plugin: same version numbers, different distribution.
CVE-2026-61991 — a CVSS 10.0 code injection flaw in the AjaxLoadMore Cache add-on for WordPress lets unauthenticated visitors execute code on your server. Affected ≤ 3.1.1; Patchstack states no official patch is available yet — deactivate the add-on. Not the free Ajax Load More core plugin: a different distribution that is not this CVE's subject.
CVE-2026-89270 — a missing-authorization flaw in the Popup Builder WordPress plugin lets an unauthenticated visitor trash every published popup on a site with a single request. Affected ≤ 4.4.5; the CVE record names NO patched version yet — update to the latest release, confirm against the vendor changelog, and check your popups' trash.
CVE-2026-39738 — an unauthenticated PHP object injection flaw in the FunnelKit Automations WordPress plugin lets visitors with no account feed the plugin booby-trapped data objects. Affected ≤ 3.8.6.1; fixed in 3.8.6.2, verified in the CVE record. Update today and review automations, contacts, and administrator accounts.
CVE-2026-61992 — an unauthenticated PHP object injection flaw in the GEO my WP WordPress plugin lets visitors with no account feed the plugin booby-trapped data objects. Affected ≤ 4.5.5.3; the CVE record contradicts itself on the fix (change-at 4.5.5.4 vs 'no patched version available') — update to the latest release (4.5.5.7 at writing) and review admin accounts and uploads.
CVE-2026-119096 — an unauthenticated authentication bypass in the Uncanny Toolkit for LearnDash WordPress plugin: the login gate looks up the raw email string while wp_signon() acts on the sanitized one, so the gate is skipped and the real account is signed in. Affected ≤ 3.8.2; the CVE record names NO patched version yet — review login activity and accounts, and update when a release names this CVE.
CVE-2026-116512 — an unauthenticated remote code execution flaw in the Project Manager WordPress plugin: the unsanitized id parameter is stitched into a validation rule string whose tokens are then invoked as PHP functions. Affected ≤ 4.1.1; the CVE record names NO patched version yet — deactivate the plugin until a release names this CVE.
CVE-2026-62131 — an unauthenticated PHP object injection flaw in the Zoho Flow WordPress plugin (Patchstack CNA, CVSS 9.8, PR:N). Affected ≤ 2.14.5; fixed in 2.14.6, verified from Patchstack (the assigning CNA) and the vendor changelog. Update today and audit admin accounts and uploaded files.
CVE-2026-109220 — an unauthenticated PHP object injection to RCE flaw in the PDF Invoice for WooCommerce + Drag and Drop Template Builder plugin: the checkout customer_note reaches unserialize() unsanitized via simplehtmldom and mPDF. Affected ≤ 7.1.1; the CVE record names NO patched version yet — disable invoice generation until a release names this CVE.
CVE-2026-103039 — an unauthenticated PHP object injection flaw in the Gravity Forms WordPress plugin: a List-type Post Custom Field value reaches maybe_unserialize() in create_post(). Affected ≤ 3.1.2; the CVE record names NO patched version yet — update and confirm with the vendor, and rework List-type post fields until then.
CVE-2026-62048 — an unauthenticated SQL injection flaw (CWE-89) in the BookIt – Booking & Appointment Calendar WordPress plugin lets a visitor with no account read the site's booking and customer database. Affected ≤ 2.6.0.6; fixed in 2.6.0.7, verified in the CVE record. Update today.
CVE-2026-115964 — an unauthenticated blind SQL injection flaw (CWE-89) in the Motors – Car Dealership & Classified Listings WordPress plugin lets a visitor with no account read the site's database one true/false answer at a time. Affected ≤ 1.4.126; fixed in 1.4.127, verified in the CVE record. Update today.
CVE-2026-76010 — an authenticated remote code execution flaw (CWE-434) in the NextGEN Gallery WordPress plugin: mass assignment, missing path containment and a bypassable signature check in render_image let a gallery owner execute code — and gallery-author access can persist after the capability is revoked. Affected ≤ 4.4.1 on 300,000+ sites; the CVE record names NO fixed version — update to the latest release and audit gallery owners.
CVE-2026-118423 — an unauthenticated arbitrary file upload to remote code execution flaw in the WP Libre Form WordPress plugin: form submissions accept PHP files with no file-type validation, and uploaded files land in a web-accessible location. Affected exactly 1.5.0.1; the CVE record names NO patched version yet — disable the plugin until a release names this CVE.
CVE-2026-118235 — an unauthenticated arbitrary file upload flaw in the SimpleForm WordPress plugin: a trailing-dot filename bypasses every extension and MIME check in handle_upload, and the only gate is a nonce printed in every public form. Affected ≤ 3.10.2; the CVE record names NO patched version yet — disable upload fields until a release names this CVE.
CVE-2026-116533 — an unauthenticated OS command injection flaw in the Static Snapshot WordPress plugin: shell metacharacters in the name parameter are concatenated into operating-system commands. Affected ≤ 0.2.1; the CVE record names NO patched version yet — remove it until a release names this CVE.
CVE-2026-118066 — an unauthenticated authentication bypass flaw (CWE-287) in the LatePoint WordPress booking plugin: the query builder pastes the literal string IS NOT NULL into SQL, so a visitor with no account can overwrite the lowest-id customer's password. Affected ≤ 5.7.6 on 100,000+ sites; the CVE record names NO fixed version — update to the latest release and audit your earliest customers.
CVE-2026-119075 — an unauthenticated privilege escalation flaw (CWE-269) in the Registration Form for WooCommerce WordPress plugin: the checkout sign-up path stores the submitted user_roles value with no allow-list check, so a guest can register as Administrator. Affected ≤ 1.1.4; fixed in 1.1.5 — update and audit your users.
CVE-2026-93389 — an unauthenticated disclosure flaw (CWE-200) in the LiteSpeed Cache WordPress plugin: WooCommerce Store API cart/checkout responses are stored as public cache objects, so one shopper's checkout details and live Cart-Token can be served to the next visitor. Affected ≤ 7.9.1 on 7,000,000+ sites; the CVE record names NO fixed version — update to the latest release.
CVE-2026-115252 — an unauthenticated remote code execution flaw (CWE-94 + CWE-862) in the Confection WordPress Cable plugin: no capability or nonce check before saving settings, and one setting is written unmodified into a standalone PHP file the plugin serves. Affected 0.4.0–0.4.7; the CVE record names NO fixed version and NO slug — remove it until a release names this CVE.
CVE-2026-123751 — an unauthenticated arbitrary file upload flaw (CWE-434) in the WP Duplicate WordPress plugin: a request authentication value is not properly verified and upload path/type are not validated, so a visitor can write arbitrary files and get RCE. Affected ≤ 1.1.11; the CVE record names NO fixed version — deactivate it until a release names this CVE. The 9.8 score is CISA-ADP enrichment; the CNA assigned none in the record.
CVE-2026-120844 — an incorrect privilege assignment flaw in the miniOrange OAuth Single Sign On (OAuth Client) WordPress plugin: the plugin that handles site sign-in assigns privileges incorrectly, letting an unauthenticated attacker escalate privileges. Affected ≤ 7.1.3; the CVE record names NO fixed version — update to the newest release and audit your users.
CVE-2026-114630 — an unauthenticated arbitrary file deletion flaw in the ELEX WordPress HelpDesk plugin: a path stored through the public ticket form is passed to unlink() by a reset page guarded only by is_admin(). Affected ≤ 3.3.8; the CVE record names NO fixed version — update to the newest release and verify your core files.
CVE-2026-107622 — an unauthenticated privilege escalation flaw in the BuddyForms WordPress plugin: a form-type confusion lets a logged-out visitor plant a rogue form whose registration creates an administrator account. Affected ≤ 2.10.5; the CVE record names NO fixed version — update to the newest release and audit your administrators.
CVE-2026-104014 — an unauthenticated authentication bypass in the Naimur Email OTP Verification for WooCommerce plugin: a verified password reset never expires, so an abandoned reset can be finished by a stranger. Affected ≤ 2.1.0; fixed in 2.1.1 — update today and review your administrator accounts.
CVE-2026-124814 — an unauthenticated arbitrary file upload flaw in the Ultimate Addons for Elementor Forms WordPress plugin: its bundled upload field validates file extensions badly, so a visitor can upload a PHP script and achieve RCE. Affected before 1.0.8; fixed in 1.0.8 — update today and scan your uploads directory.
CVE-2026-124647 — an unauthenticated SQL injection flaw in the TI WooCommerce Wishlist WordPress plugin: the tinv_wishlistkey cookie feeds a SQL statement unsanitised. Affected before 2.0.7; fixed in 2.0.7 — update today and review your database logs.
CVE-2026-89324 — an improper authentication flaw (CWE-287) in the Basel Post Types WordPress plugin bundled with the Basel WooCommerce theme: a hardcoded fallback salt lets an unauthenticated attacker forge a social-login callback and sign in as any user, admins included. Affected ≤ 1.18; the CVE record names NO fixed version — update Basel to the newest release and disable social login until patched.
CVE-2026-126173 — a missing authorization flaw (CWE-862) in the AutomatorWP Pro Webhooks addon for WordPress: an unauthenticated attacker can reset any account's password, admins included, where a webhook automation updates user passwords. Affected ≤ 1.4.4; the CVE record names NO fixed version — update AutomatorWP Pro to the newest release and audit webhook automations.
CVE-2026-126187 — an unauthenticated remote code execution flaw (CWE-502) in React Server Components: crafted Flight payloads against react-server-dom-* 19.0.0–19.0.8, 19.1.0–19.1.9, 19.2.0–19.2.8 and 19.3.0. Fixed in 19.0.9 / 19.1.10 / 19.2.9 / 19.3.1. The record limits reachability to extremely rare cases — check your lockfile.
CVE-2026-116615 — an authenticated code injection flaw in the Widget Options WordPress plugin: the save-time filter and the render-time parser read the same block comment differently, so Author-level logic reaches @eval. Affected ≤ 4.2.6.1; the CVE record names NO fixed version — update to the newest release and audit authors.
CVE-2026-19907 — an unauthenticated authentication bypass in the Shipo WordPress plugin: it authenticates the username inside the logged-in cookie without verifying the cookie's signature. Affected 1.6–1.8.0; the CVE record names NO fixed version — update to the newest release and audit admins.
CVE-2026-119077 — an unauthenticated PHP object injection flaw in the ELEX WordPress HelpDesk plugin: it deserializes an attacker-controlled form field guarded only by a nonce printed on the public support form. Affected ≤ 3.3.9; the CVE record names NO fixed version — update to the newest release and audit admins.
CVE-2026-119516 — a deserialization of untrusted data (PHP object injection) flaw in the Radius Booking WordPress appointments plugin: the plugin unserializes attacker-controlled data, reachable with no account at all. Affected ≤ 1.0.20; the CVE record names NO fixed version — update to the newest release and audit your users.
CVE-2026-118267 — an incorrect authorization flaw (CWE-863) in the WP Data Access WordPress plugin: the write endpoints skip the row/column restrictions the read endpoints enforce, so a Subscriber on a site with a published write-enabled Data App can overwrite the administrator's password hash. Affected ≤ 5.5.89; the CVE record names NO fixed version — update to the latest release.
CVE-2026-100109 — an unauthenticated administrator-creation flaw (CWE-862) in the Security For WooCommerce WordPress plugin: a user-creation action available to unauthenticated visitors performs no capability check and lets the caller pick the role. Affected 1.0.10 through 1.0.16; the CVE record names NO patched version yet — disable it and audit your users.
CVE-2026-65555 — an unauthenticated privilege escalation flaw (CWE-266) in the Uncanny Toolkit for LearnDash WordPress plugin lets a visitor with no account escalate to a privileged role. A second, distinct critical flaw in the same ≤ 3.8.2 range as last week's auth bypass. Fixed in 3.8.3, verified in the CVE record. Update today and audit your admin users.
CVE-2026-119481 — an unauthenticated privilege escalation flaw (CWE-266) in the JetFormBuilder WordPress plugin lets a visitor with no account escalate to a privileged role. Affected ≤ 3.6.7.1; fixed in 3.6.8, verified in the CVE record. Update today and audit your admin users.
CVE-2026-89435 — an authenticated (Subscriber+) arbitrary plugin installation flaw in the Formidable Forms WordPress plugin: a token-only permission check plus insufficient download-URL validation. Affected ≤ 6.35; the CVE record names NO fixed version — update to the latest release (7.0 at writing, whose changelog hardens exactly these two points) and audit your installed plugins and admin accounts.
Firebase is the default backend for AI-built apps — and its web config is public by design, so your rules file is the only lock on your data. The 5 open-database mistakes AI builders ship, starting with test-mode rules left in production.
Supabase is safe exactly as long as Row Level Security holds — with RLS off or policies missing, the anon key in your client code is a skeleton key. The pre-launch checklist: RLS on every table, a policy per operation, no using(true), service_role nowhere near the client.
In Next.js, only NEXT_PUBLIC_ variables are meant to reach the browser — but renaming a key to fix an undefined error publishes it, and server-module imports leak too. What actually ends up in your bundle, and how to grep for it.
An AI agent built your app and you can't read the code — how do you know it's safe to launch? The 5 checks that decide it: database rules, bundled secrets, logged-out access, disclosures, and the patch story — plus what no outside check can tell you.
Plugin updates are one layer. xmlrpc left on, user enumeration wide open, readme files announcing your versions — the WordPress hardening steps for AI-built sites that sit underneath the CVE of the week.
The free Newsletters plugin (newsletters-lite) shipped two critical flaws at once: an unauthenticated SQL injection (CVE-2026-111402, 9.3) and an unauthenticated PHP object injection (CVE-2026-94075, 9.8), both in versions ≤ 4.18.1. Fixed in 4.18.2 — then rotate your salts and reset admin passwords.
Product Filter by WBW takes input from every storefront visitor — and in versions ≤ 3.4.6 it reaches the database unsafely: an unauthenticated blind SQL injection (CVE-2026-112866, CVSS 9.3). Fixed in 3.4.7.
Paytium, the WordPress plugin for Mollie payment forms and donations, has an unauthenticated PHP object injection scoring 9.8 (CVE-2026-114196) in versions ≤ 5.0.5. Fixed in 5.0.6 — whatever ingests data patches first.
On a site with open registration, any signed-up Contributor can promote themselves to Editor in aBlocks ≤ 2.17.0 (CVE-2026-110018, CVSS 8.8 — authenticated precondition, stated straight). No fixed version is verified yet; update when one lands, and audit your user roles now.
An AI code review reads your repo; your users visit the deployment. Production headers, live plugin versions matched against same-day CVE data, checks on apps you didn't write, a deterministic score with a shareable proof link, and monitoring that re-checks — the honest case for a live outside-in scan next to the LLM review you already run.
We passively checked 137 freshly launched homepages — Show HN, Product Hunt, TinyLaunch. 4 in 30 sent the full security-header set, 60% had no CSP, and 3 sent nothing at all. What new launches actually ship, from our own outreach telemetry.
CVE-2026-124815 — an unauthenticated SQL injection flaw (CVSS 10.0*, CISA-ADP enrichment; the WPScan CNA assigned no score) in the Clockinator Lite WordPress plugin: several record deletion actions restrict nothing, and a user-supplied table name reaches a SQL query unvalidated, so a visitor with no account can delete data from any table and extract password hashes. Affected before 1.1.0; fixed in 1.1.0, verified in the CVE record. 80 active installs.
CVE-2026-125795 — an unauthenticated local file inclusion flaw (CWE-98, CVSS 9.8) in the Estatik WordPress real-estate plugin: improper control of a filename for include/require lets a visitor with no account influence which PHP file the server includes. Affected ≤ 4.3.6; fixed in 4.3.7, verified in the CVE record. 10,000 active installs.
CVE-2026-40217 — a sandbox escape in LiteLLM's custom-code guardrail (CWE-420, CVSS 8.8): POST /guardrails/test_custom_code escapes via bytecode techniques to RCE in the proxy process. Affected >= 1.81.8, < 1.83.10 (GHSA-wxxx-gvqv-xp7p); added to CISA KEV 2026-11-18 with exploitation active. Upgrade to the newest 1.83.x — check your lockfile.
WordPress 7.1.5 (Nov 18, 2026) fixes a Template Part flaw Wordfence classifies as a client-side CSRF, CVSS 8.8: a crafted editor link an admin opens creates a new Administrator account. Affected Core 5.9.0–7.1.4, patched per branch through 7.1.5. No CVE assigned yet; RCE was not demonstrated.
CVE-2026-126714 (CVSS 9.2, v4.0): PHP's default files session handler updates session files in place without clearing them — an interrupted write leaves old session bytes that later unserialize as objects. Affected before 8.2.36 / 8.3.37 / 8.4.28 / 8.5.13, fixed Nov 19, 2026. Four preconditions, gadget chain included.
CVE-2026-110811 (CVSS 9.8): Trust Payments Gateway for WooCommerce stores the raw wp_create_user() return — including a WP_Error on username collision — as the order's user ID before the error check, and the thank-you page acts on it. Affected ≤ 1.3.8; no fixed version named in the CVE record.
CVE-2026-110009 (CVSS 9.8): Unzer Payments for WooCommerce resolves a submitted email address to any existing WordPress user — including administrators — and issues that user's session cookies, with no proof of payment or ownership. Affected ≤ 2.2.1; no fixed version named in the CVE record.
The PreShipIt Brief — a short weekly email for people shipping vibe-coded apps: the week's important vulnerabilities and launch-safety checks, in plain English.
New and free. Double opt-in: we email you a confirmation link before anything else arrives. Unsubscribe any time.
← Back home · Run a free mini-scan · Scan my app — $29 · See a sample report