Blog

What the engine found

Disclosures from pointing it at code nobody had audited, and what the pattern behind each one means for anything else built the same way.

7.6

High · CVSS 4.0

26 October 2026

The vault that let you spell your way past a deny rule

OpenBao is an open-source secrets manager, and a deny rule is the strongest line in its policies. A fix in September was meant to close the ways around those rules, and it missed resources in four authentication plugins. Spell the name differently and the deny did not apply. Public as GHSA-736f-82w7-hj22, rated High, 7.6 of 10 on CVSS 4.0, fixed in 2.7.2 and in the 0.2.0 LDAP and RADIUS plugins.

Read it →GHSA-736f-82w7-hj22 · CWE-863

7.5
High
19 October 2026
The two-factor plugin that let attackers bring their own passkey
A two-factor plugin added passkeys, and an older guard that fit codes sent to an email address or a phone did not fit the new method. Anyone who knew the password of a user who signs in with a passkey could add their own passkey to that account in the middle of the login, then sign in with it. Public as CVE-2026-111949, scored 7.5 of 10 by WPScan, fixed in 6.3.1.
5.5
Medium
19 October 2026
One nonce, every post on the site
A pricing-table plugin checked that a token was valid, but not which post it was for. A contributor could reuse the token from their own draft to copy any post on the site, private pages and other people's drafts included, and the copy came out published. Public as CVE-2026-111947, scored 5.5 of 10 by WPScan, fixed in 4.1.3 per WPScan.
7.2
High
16 October 2026
The fix that forgot about capital letters
An earlier privilege-escalation fix in a booking plugin, as written, blocked almost every name, capitals included. The next release made it exact, and exact meant case-sensitive, while the database is not. Spelled in capitals, the same profile entry walked past the guard, and a salon staff account could make any account an administrator. Public as CVE-2026-110031, scored 7.2 of 10 by WPScan, fixed in 10.31.11.
5.3
Medium
16 October 2026
They fixed this file. The hole stayed.
A WordPress plugin loaded one small file on every request, and it let any anonymous caller write data into one of the site's settings and serve it back as a redirect. A security fix had already gone through that file. Nobody added a permission check. Public as CVE-2026-94294, scored 5.3 of 10 by WPScan, fixed in 5.7.1.
5.9
Medium
14 October 2026
The human sign-off an AI agent never needed
An enterprise AI platform let operators require a human to approve an AI agent's risky tool calls. Add a narrow exception before the broad rule, and any call that matched both needed no approval, while the rule stayed on screen looking enforced. Public as GHSA-mr62-rhg7-9m4v, rated Medium, 5.9 of 10, fixed in platform-v1.3.73.
8.6
High
9 October 2026
The verification code you never needed
The same WordPress plugin that would email a code to any address also checked codes with a SQL query it built by pasting the values in, then handed the finished string to prepare(). In our lab, one anonymous request made the check say yes without the code. Public as CVE-2026-89299, scored 8.6 of 10 by WPScan, no patch.
8.6
High
9 October 2026
The 2FA plugin that answered questions about your password hashes
A WordPress plugin built as a second factor for logins took a value from an anonymous request, cleaned it as an email address, and pasted it into SQL. Anyone could ask the users table yes-or-no questions, password hashes included. Public as CVE-2026-89213, scored 8.6 of 10 by WPScan, no patch.
8.8
High
7 October 2026
We turned Argo CD's proxy field into a shell
Argo CD copied one repository setting, the proxy for an SSH repo, into a shell command. Anyone allowed to add or edit a repository could run commands inside the component that holds the credentials for other repositories. Public as CVE-2026-55797, scored 8.8 of 10 by the Argo CD maintainers.
8.4
High
26 September 2026
One tool call out of the AI sandbox
An MCP server promised its AI agent could never touch a file outside the project folder. One tool call with the right path could read, overwrite or delete anything the server could reach. Public as GHSA-rxhw-rjp6-53vj, rated High, 8.4 of 10.
3.7
Low
18 September 2026
A sign-in finished by someone else
An OAuth callback meant to redeem a sign-in code from a merchant's own connected account instead accepted one from any anonymous visitor, on every request to the site, and overwrote the store's connection to its ad platform with whatever code the request carried. Public as CVE-2026-92965, scored 3.7 of 10 by WPScan.
5.3
Medium
18 September 2026
The verification email you never asked for
A REST route built to email a verification code to whoever asked for one never checked that the asker and the recipient were the same person, so any anonymous caller could name any address on the internet and the site would email it, no rate limit, no fix. Public as CVE-2026-89300, scored 5.3 of 10 by WPScan.
6.5
Medium · our score
8 September 2026
Redacted, except for the card number
A redaction library that scrubs card numbers out of text before it reaches a log or an AI model said the job was done. Put an accented letter, a Russian greeting or a few emoji in front of the number and part or all of it came through anyway. Public as GHSA-gwjv-qpf9-g36x, rated Medium, with sibling advisories in two more SDKs.
4.3
Medium
7 September 2026
The cookie banner anyone could reset
Two AJAX actions meant to load a cookie-consent plugin's built-in A/B presets carried no capability check and no nonce, so any logged-in Subscriber could fire them and replace the administrator's configured banner, for every visitor, and erase whatever the real test had been measuring. Public as CVE-2026-82185, scored 4.3 of 10 by WPScan.
5.3
Medium
3 September 2026
A review for a place you've never been
A field meant to hold the site owner's own Google Place ID never checked whether they had configured that place, so any visitor could send it any ID and watch the site pay Google for the answer. Public as CVE-2026-84936, scored 5.3 of 10 by WPScan.
7.4
High
2 September 2026
Three characters from a broken homepage
A public form field meant to name an upload folder let an unauthenticated visitor point it at the site root instead, deleting the files WordPress needs to serve the homepage. Public as CVE-2026-81347, scored 7.4 of 10 by WPScan.
9.8
Critical
20 August 2026
The password you never needed
A convenience feature in a plugin that had nothing to do with authentication became a full account takeover. Public as CVE-2026-77264, scored 9.8 of 10 by Wordfence.

See what a scan turns up

Nominate a target. The first scan costs nothing, and we’ll walk you through it.

Get a free scan See the pricing

What the engine found

The vault that let you spell your way past a deny rule

The two-factor plugin that let attackers bring their own passkey

One nonce, every post on the site

The fix that forgot about capital letters

They fixed this file. The hole stayed.

The human sign-off an AI agent never needed

The verification code you never needed

The 2FA plugin that answered questions about your password hashes

We turned Argo CD's proxy field into a shell

One tool call out of the AI sandbox

A sign-in finished by someone else

The verification email you never asked for

Redacted, except for the card number

The cookie banner anyone could reset

A review for a place you've never been

Three characters from a broken homepage

The password you never needed

See what a scan turns up