The 9 November batch holds forty-seven records, all published on 8 November, and none of them appears in the CISA known exploited catalog released on 9 November 1. Twenty-two are WordPress plugins, thirteen Hickory DNS, five rustls, three imgproxy, and four others. Three of those plugins hand an unauthenticated visitor an administrator account.
Four plugins, three that end with an administrator account
CVE-2026-110963 covers Userplace through 1.2.0, where an AJAX action open to unauthenticated users has no authorization check and exposes the nonce that guards it. A visitor can create an administrator account or write arbitrary options 2.
CVE-2026-106015 covers Ecommerce Affiliate through 1.0.0, where OTP issuance and verification run without restriction or attempt limit. A visitor can take over any account on the site, administrators included 3.
CVE-2026-104338 sits in Razorpay for WooCommerce before 4.8.9. A REST route takes the acting user from a parameter the caller supplies, so one request acts as any user when a particular coupon is active 4.
Contact Form 7 before 6.2.4 is the one I read twice. CVE-2026-114432 lets an unauthenticated visitor upload a file whose type and extension the plugin never checks, and a cleanup flaw leaves it on disk 5. A stock Debian or Ubuntu Apache that lists directories and maps .phar to PHP will run it. Elsewhere the file lands in the uploads directory and can still render as HTML or SVG from the site’s own origin 5.
None of the four has a report of exploitation behind it, and my blog is static, so none of it applies there. The rest of the plugin set includes unauthenticated SQL injection in Productive Commerce before 1.1.54 6 and a BackUpWordPress cleanup action before 3.15 that deletes backups without a capability check 7. I would order by what is installed, because a plugin that is not installed has nothing to exploit.
An image proxy with a heap write in the ICO loader
imgproxy 4.0.0 through 4.0.15 carries CVE-2026-123614: a crafted data_size value overflows an integer, wraps the allocation in vips/icoload.c and corrupts heap memory, which ends in a crash or code execution 8. Unbounded allocation from an invalid data_size crashes workers without authentication in 3.3.0 before 4.0.16 9, and 3.3.0 before 4.0.17 has an out-of-bounds heap read and write during ICO BMP header reconstruction 10. 4.0.16 closes the first two, and the header write needs 4.0.17.
An image proxy takes files from places it does not control, often from a user-supplied URL, so the image arrives without a login.
Thirteen Hickory DNS records, seven of them validation
Hickory DNS ships thirteen records, seven of them ending with a validating resolver accepting an answer it should have rejected. The clearest is CVE-2026-123605, where the validator checks an RRSIG against the DNSKEY of whatever name sits in the Signer’s Name field without confirming that name owns the record set. Anyone who controls a DNSSEC-signed zone can sign records in unrelated zones, and resolvers, recursors and clients using DnssecDnsHandle take them as authenticated 11. The other six fail on checks that ignore the DNS class or accept NSEC and NSEC3 proofs borrowed from a parent-side ancestor delegation.
The remaining six are four denial-of-service records, one ghost-domain caching flaw and one filtering check that misreads IPv4-mapped addresses. CVE-2026-123602 is the odd one, where the recursor reuses a child-side apex NS RRset cached from zone NS queries, so a zone whose delegation the parent revoked keeps answering 12. CVE-2026-123608 is the plainest, quadratic-time name compression in BinEncoder, where one hostile response spends the resolver’s CPU 13. Fixes land at hickory-proto 0.26.1 and 0.26.2, hickory-net 0.26.1 and 0.26.2, and resolver 0.26.2, so the pin depends on the crate. A bypass needs a signed zone, which costs a domain and a key, and the payoff is a record in someone else’s zone.
rustls, five records and a logging leak
CVE-2026-123611 affects rustls before 0.23.46. A network attacker answers one connection with a ServerHello that selects X25519, which poisons the per-server-name key-exchange group record, so later ClientHellos to that name carry only classical shares and the post-quantum confidentiality is gone until the cache turns over 14.
CVE-2026-123609 affects builds before 0.23.46, and 0.24.0-dev.1 before 0.24.0-dev.2, where Debug formatting of client session values puts secret key material in front of whoever reads the logs 15. The other three cover wrong-level handshake messages, application data disclosed when ECH is rejected, and Brotli decompression with an input-chosen window.
These go last. The debug leak is the one I would handle by hand, because a key in a log file is also a key in a backup and in whatever ships the logs.
Four that fit no family
UnrealIRCd 6.0.0 before 6.2.7.1 has CVE-2026-114713, where the labeled-response module does not escape the IRCv3 label tag when it echoes the tag into a reply. Any user on a network with two or more linked servers can inject server-to-server commands with server authority 16.
FlowCI flow-core-x up to 1.23.49 has CVE-2026-124328, code injection through ConditionManagerImpl.run in the Groovy script evaluation, reachable remotely 17. A build server holds the tokens for everything it deploys, so that one is a credential question as much as a code question. Dinky and SunEditor fill out the four.
What I would send
The plugin list goes to whoever owns those sites, ordered by what is installed. The crate records belong in the next dependency update, and the debug-logging one gets a search through whatever keeps logs.
None of this carries a deadline, which is why I would move now. A batch like this sits in a backlog until something else makes it urgent.
-
CISA. (2026, November 9). Known exploited vulnerabilities catalog (version 2026.11.09). CISA. https://www.cisa.gov/known-exploited-vulnerabilities-catalog ↩︎
-
Tenable. (2026, November 8). CVE-2026-110963. Tenable. https://www.tenable.com/cve/CVE-2026-110963 ↩︎
-
Tenable. (2026, November 8). CVE-2026-106015. Tenable. https://www.tenable.com/cve/CVE-2026-106015 ↩︎
-
Tenable. (2026, November 8). CVE-2026-104338. Tenable. https://www.tenable.com/cve/CVE-2026-104338 ↩︎
-
Tenable. (2026, November 8). CVE-2026-114432. Tenable. https://www.tenable.com/cve/CVE-2026-114432 ↩︎ ↩︎
-
Tenable. (2026, November 8). CVE-2026-109925. Tenable. https://www.tenable.com/cve/CVE-2026-109925 ↩︎
-
Tenable. (2026, November 8). CVE-2026-104307. Tenable. https://www.tenable.com/cve/CVE-2026-104307 ↩︎
-
Tenable. (2026, November 8). CVE-2026-123614. Tenable. https://www.tenable.com/cve/CVE-2026-123614 ↩︎
-
Tenable. (2026, November 8). CVE-2026-123616. Tenable. https://www.tenable.com/cve/CVE-2026-123616 ↩︎
-
Tenable. (2026, November 8). CVE-2026-123615. Tenable. https://www.tenable.com/cve/CVE-2026-123615 ↩︎
-
Tenable. (2026, November 8). CVE-2026-123605. Tenable. https://www.tenable.com/cve/CVE-2026-123605 ↩︎
-
Tenable. (2026, November 8). CVE-2026-123602. Tenable. https://www.tenable.com/cve/CVE-2026-123602 ↩︎
-
Tenable. (2026, November 8). CVE-2026-123608. Tenable. https://www.tenable.com/cve/CVE-2026-123608 ↩︎
-
Tenable. (2026, November 8). CVE-2026-123611. Tenable. https://www.tenable.com/cve/CVE-2026-123611 ↩︎
-
Tenable. (2026, November 8). CVE-2026-123609. Tenable. https://www.tenable.com/cve/CVE-2026-123609 ↩︎
-
Tenable. (2026, November 8). CVE-2026-114713. Tenable. https://www.tenable.com/cve/CVE-2026-114713 ↩︎
-
Tenable. (2026, November 8). CVE-2026-124328. Tenable. https://www.tenable.com/cve/CVE-2026-124328 ↩︎