WordPress security news, 16 November 2026: a critical Apache HTTP/2 flaw, and file flaws with no login needed
The item that matters most this week is not in WordPress. Apache httpd 2.4.71, released on 11 November, fixes CVE-2026-119618, a critical race in mod_http2 that can lead to remote code execution on any server running 2.4.55 through 2.4.70 with HTTP/2 enabled. That range includes 2.4.70, the release last week’s briefing recommended. A public proof of concept crashes Apache without running code, but Red Hat is quoted as saying public research has shown a reliable exploit against a default configuration; nobody has reported exploitation in the wild. On the plugin side, Patchstack marks the AutomatorWP Pro Webhooks add-on and wpForo’s two SQL injections as exploited, and three form and upload add-ons disclosed unauthenticated file upload, write or deletion flaws, each rated 10. Quick Page/Post Redirect, closed on WordPress.org in April for a backdoor delivered in 2021, now has a CVE, so scanners will start flagging the 70,000 sites that had it. ELEX HelpDesk has a public exploit for an object injection. Wordfence counted 497 new vulnerabilities in the week to 8 November. Two items are for the calendar: OpenSSL announced five low-severity fixes due on 1 December, and WordPress 7.2 reaches release candidate on 17 November with a Secrets API that is off unless the site has a key.
Prepared by G. Schad, WordPress and Linux security specialist
CVE-2026-119618, critical: mod_http2 heap corruption and RCE in 2.4.55–2.4.70 when HTTP/2 is on. Fixed in 2.4.71 (11 November). Public PoC crashes Apache; Red Hat reportedly says a reliable exploit has been shown. No reported exploitation, not in KEV as of 13 November
Plugins
Exploited per Patchstack: AutomatorWP Pro Webhooks ≤ 1.4.4 (fix 1.4.5). CVSS 10, no login: Ultimate Addons for Elementor Forms < 1.0.8 (upload), Cloud Storage Manager for Fluent Forms ≤ 1.2.0 (write), File Upload to Order < 1.1.4 (deletion)
Remove
WP Duplicate: exploited, no fix. Quick Page/Post Redirect: backdoor in 5.2.1–5.2.3, now CVE-2026-126697, and the plugin cannot be downloaded
Calendar
OpenSSL 4.1.1, 4.0.4 and 3.5.10 on 1 December, five low-severity fixes. WordPress 7.2 RC1 on 17 November, final release 8 December
This week in one minute
The short version: what changed in the week to 16 November
If you read one section, read this one. The first job this week is on the server, not in WordPress. Apache’s mod_http2 has a critical flaw in every release from 2.4.55 to 2.4.70, and it is reached by an HTTP/2 request before PHP or WordPress runs, so no WordPress security plugin sees it. The fix is 2.4.71 or a distribution package that lists the CVE. If you cannot patch today, turning HTTP/2 off closes it. Last week’s advice to move to 2.4.70 is superseded: 2.4.70 is the last affected release.
For plugins, sort by what an anonymous visitor gets. Files: Ultimate Addons for Elementor Forms uploads them, Cloud Storage Manager for Fluent Forms writes them, and File Upload to Order deletes them. A deleted wp-config.php is a route to takeover too. Accounts: the AutomatorWP Pro Webhooks add-on, which Patchstack has seen exploited, along with Shipo and User Verification. The database: wpForo, whose two SQL injections are exploited too. Two plugins have to go. WP Duplicate still has no fix. Quick Page/Post Redirect carried a hidden update channel that delivered a tampered build in 2021, and it cannot be downloaded in a clean version.
Figure 1 · The week at a glance
The web server comes first this week, then plugin flaws that need no login.
UA for Elementor Forms · Cloud Storage Mgr · File Upload to Order
CVSS 10, no login: upload, write, delete
1.0.8 · 1.2.5 · 1.1.4; check uploads
WP Duplicate · Quick Page/Post Redirect
Exploited, no fix · backdoor, plugin closed
Export redirects; delete both
ELEX HelpDesk ≤ 3.3.9 · Bricksforge ≤ 3.1.8.9
Public PoC · exploited per Patchstack
ELEX 3.4.0 · Bricksforge 3.1.8.10
OpenSSL · WordPress 7.2
Low fixes on 1 Dec · RC1 17 Nov, final 8 Dec
Schedule; test the Secrets API on staging
The six items that need action in the week to 16 November 2026: Apache’s HTTP/2 flaw, an exploited webhook add-on, three file flaws, two plugins to remove, a public exploit, and two dates for the calendar.
Apache · CVE-2026-119618
Critical mod_http2 race, heap corruption and possible RCE in 2.4.55 to 2.4.70, only with h2 or h2c enabled. Found independently by Anthropic’s OSS Scanner and Google Cloud Vulnerability Research. Fixed in 2.4.71. A public PoC reproduces the crash; Red Hat is quoted as saying a reliable exploit has been shown. Nothing seen in the wild.
Plugins · exploited and CVSS 10
AutomatorWP Pro Webhooks is exploited, through a password reset in one webhook configuration. Three file flaws need no login: an upload, a write and a deletion. wpForo’s two unauthenticated SQL injections are exploited as well; go to 3.2.5.
Plugins · remove
WP Duplicate is unchanged from last week: exploited, with no fix. Quick Page/Post Redirect’s 2021 backdoor now has a CVE. The plugin has been closed since April, so delete it rather than update it, after exporting the redirects.
Calendar · OpenSSL and WordPress 7.2
OpenSSL ships five low-severity fixes on 1 December; none affects ordinary TLS. WordPress 7.2 RC1 is on 17 November. Its Secrets API needs a WP_SECRETS_KEY that upgraded sites will not have, and a /random/ route that needs a rewrite flush.
Full write-ups
The week to 16 November, item by item: where each is covered in full
The mechanism, affected versions, indicators and commands for each item are on the page named beside it. Those pages are updated as each story moves; this briefing stays as the record of the week.
This week’s item
Covered in full on
Apache 2.4.71: a critical mod_http2 flaw in every release since 2.4.55, including 2.4.70
WordPress 7.2: the Secrets API is off unless the site has a key, and three things to test before 8 December
WordPress 7.2 reaches release candidate on 17 November and ships on 8 December. The Hosting Team’s call to test, posted on 12 November, names three things hosts should try now. The headline is the Secrets API, a Core way to store credentials such as API keys encrypted rather than in plain options. It is disabled on any site without a WP_SECRETS_KEY constant, and returns secret_key_unavailable. Beta 5 removed the fallback to the salts, and only the browser installer writes a key. Sites that are upgraded, or created with wp config create or a one-click installer, will have no key until someone adds one.
The other two are about upgrades. A Dashboard upgrade from 7.1.4 leaves ten files under wp-includes/ that a WP-CLI upgrade removes. wp core verify-checksums reports them as warnings but still exits 0, so a monitoring script that only checks the exit code will pass. And a new /random/ route returns a 404 after an upgrade until the rewrite rules are flushed. Separately, drop-ins written against the Beta 4 interfaces cause a fatal error until they are changed to extend the new classes.
One question is still open. A 13 November update to the post notes a comment asking for the Secrets API to be pulled from 7.2, and the API’s author asking for a real hosting-provider implementation first. Test on staging only. Before 8 December, decide how WP_SECRETS_KEY will be generated, stored and backed up for each site, because secrets encrypted with a key cannot be read without it.
Core, PHP2Shell, nginx and Brotli: status on 16 November
WordPress Core · CVE-2026-119977
No technical change. It is still in CISA’s catalog. 7.1.4 or the branch backport remains the fix, with wp-content/upgrade/ denied at the web server. Free Wordfence installs receive the firewall rule on 27 November.
PHP · PHP2Shell
No new PHP release this week. 8.5.12, 8.4.27, 8.3.36 and 8.2.35 remain the fixed versions, and CVE-2026-115560 still waits for the next release. PHP 8.6.0 is due on 19 November.
nginx
Stable 1.30.6 and mainline 1.31.8 are still the releases to run. A server patched only to 1.30.1 for CVE-2026-42945 in May is a dozen advisories behind.
Brotli · CVE-2026-111497
CISA’s deadline passed on 10 November, with nothing new since. Where the library has been updated, check that no process still has the old copy loaded.
What this week means: the web server is part of the WordPress attack surface
In most weeks the WordPress risk is in plugins, and the server shows up as the second step of a chain. This week the first step is the server itself: a request to Apache over HTTP/2 that never reaches PHP or WordPress. No WordPress security plugin sees it, and no plugin update fixes it. The inventory that answers it is per server, not per site: which web server, which version, and which protocols on which virtual hosts.
The plugin side repeats last week’s lesson with a twist. The worst entries, uploading, writing and deleting files without a login, are in small form and upload add-ons: the kind of plugin that gets installed for one form and forgotten. Quick Page/Post Redirect and WP Duplicate make the same point about utility plugins. A redirect or migration plugin that did its job years ago is still running code on every request.
The rule that follows is simple and dull: every plugin on a site should have a reason to be there this month. Redirects belong in the server configuration once they are stable, migration plugins come out when the migration is done, and form add-ons are reviewed along with the form.
The full checks, including the changelog test for backported packages and the look-back, are in the CVE-2026-119618 advisory linked below.
02
Update the exploited and the CVSS 10 plugins
List them, with their versions, across every site on the server:
shell
$ for s in /home/*/public_html;dowp plugin list --path="$s"--skip-plugins--skip-themes--fields=name,version--format=csv2>/dev/null|grep-E"^(automatorwp-webhooks|wpforo|bricksforge|ultimate-addons-for-elementor-forms|cloud-storage-manager|file-upload-to-order|elex-helpdesk-customer-support-ticket-system),"|sed"s|^|$s |";done
Targets: AutomatorWP Pro Webhooks 1.4.5, wpForo 3.2.5, Bricksforge 3.1.8.10, Ultimate Addons for Elementor Forms 1.0.8, Cloud Storage Manager for Fluent Forms 1.2.5, File Upload to Order 1.1.4, ELEX HelpDesk 3.4.0. Premium plugins’ folder names can differ, so check by title as well.
03
Remove WP Duplicate and Quick Page/Post Redirect
WP Duplicate has no fix, and a clean Quick Page/Post Redirect cannot be downloaded. Run the update-channel and file checks and export the redirects first, as the Quick Page/Post Redirect advisory below describes, then delete both:
Running the checks first keeps the evidence from being deleted along with the folder.
04
Check the file-flaw sites
On any site that ran a vulnerable version of the upload, write or deletion plugins, look for PHP files in uploads by date, and check that wp-config.php and .htaccess are still in place:
shell
$ find /home/*/public_html/wp-content/uploads -type f \( -iname"*.php*"-o-iname"*.phar"-o-iname"*.pht" \) -newermt"2026-10-15"-ls
05
Review accounts where takeover was possible
AutomatorWP Pro Webhooks, Shipo, User Verification and Advanced Form Integration can all hand out accounts or roles. On sites that ran them, review administrators and recent password resets:
WP-CLI
$ wp user list --role=administrator--fields=ID,user_login,user_registered--skip-plugins--skip-themes
The next 48 hours, and the hardening that keeps this week from repeating
24 to 48 hours · the rest of the table
Shipo 1.8.1, Advanced Form Integration 2.11.5, User Verification 2.0.49, Everest Forms at the current release, Drag and Drop File Upload for Elementor Forms after 1.6.2, and Ultra Addons for Contact Form 7 at 3.5.55 or later. Then the roundup items, in the normal cycle.
24 to 48 hours · the Apache look-back
On servers that ran an affected Apache with HTTP/2 on, check for segfaults in the error log since 11 November, and for processes started by the web server that are not PHP. Copy the logs off the server first.
This week · redirects into the server configuration
Move stable redirects out of plugins and into .htaccess or the nginx configuration. There they cost nothing at runtime, and nobody else can update them.
This week · a protocol inventory
Record, per server and per virtual host, the web server, its version and the protocols it speaks. Fleets that already had this answered this week’s question in minutes.
Before 8 December · WordPress 7.2
Test the upgrade on staging, decide how WP_SECRETS_KEY is provisioned and backed up, and add wp rewrite flush to the upgrade runbook.
1 December · OpenSSL
Schedule the distribution updates for after the 1 December releases, with a restart of everything that links the library.
Checklist
Thirty minutes per server: the ten checks that close this week
01
Apache 2.4.71 or a fixed package on every server that ran 2.4.55 to 2.4.70
Confirmed from the running binary and the package changelog, not the mod_http2 version string.
02
Or HTTP/2 off until then
Every Protocols line set to http/1.1, the configuration checked, and Apache restarted.
03
No segfault runs or web-server shells since 11 November
Error logs and the process tree read, and the result noted.
04
AutomatorWP Pro Webhooks at 1.4.5
Password resets and administrator logins reviewed wherever the add-on was active.
05
The three CVSS 10 file flaws closed
Ultimate Addons for Elementor Forms 1.0.8, Cloud Storage Manager 1.2.5, File Upload to Order 1.1.4.
06
wpForo at 3.2.5 and Bricksforge at 3.1.8.10
Moderator and administrator passwords reset on any forum that ran 3.2.2 or earlier.
07
WP Duplicate and Quick Page/Post Redirect removed
Redirects exported first, and the update-channel and file checks run with their result noted.
08
ELEX HelpDesk at 3.4.0, or removed
Its third unauthenticated flaw in a month.
09
Uploads checked, and the files a deletion would target still present
No unexpected PHP in uploads; wp-config.php and .htaccess in place.
10
Logs preserved and a ticket opened for every match
Anything above that matched gets a case, with the logs copied off the server before cleanup starts.
Sources
Where every claim in this briefing comes from
This briefing was compiled on 16 November 2026. Versions, dates and figures are quoted as the source reported them and were not independently re-measured. The Apache facts (affected range, credits, dates, fix commit and the two other CVEs) are from Apache’s vulnerability page and release announcement. The HTTP/2 condition, Red Hat’s score and its RHEL ratings are from Red Hat’s CVE page. The CNA score, the Wiz statement and telemetry, SecurityWeek’s report of the public proof of concept, the KEV status on 13 November, the RHEL 8 status and the distribution packages are from Rescana’s compilation, updated 13 November; we did not read the Wiz or SecurityWeek posts directly. The description of the one-line fix comes from published patch-diff analyses and was not checked against the commit. Plugin facts are from the Patchstack entries linked in each section, read on 16 November, and from the WordPress.org listings and changelogs. WP Duplicate’s status is WPScan’s. The Quick Page/Post Redirect history is BleepingComputer’s account of Austin Ginder’s findings; the CVE, the affected range and the score are Patchstack’s; the plugin’s closure is from WordPress.org. The ELEX proof of concept, its mechanism, and the CVE identifiers for wpForo, ELEX and Ultimate Addons for Elementor Forms are from secondary reporting. The Wordfence numbers are from its weekly report as published in Wordfence’s feed. The OpenSSL details are from the advisory as posted to oss-security, and the WordPress 7.2 details are from the Hosting Team’s call to test.
The research notes this issue started from were corrected where the sources disagreed. File Upload to Order is described as a file deletion, not an upload, by the CVE record and Patchstack’s entry title. Wordfence’s 21 is every critical entry, not 21 unauthenticated code-execution flaws. Patchstack scores wpForo’s SQL injections 9.3, not 7.5, and Advanced Form Integration 9.8 with a fix in 2.11.5. ELEX’s flaw is CVE-2026-125855 at Patchstack, with a possible collision noted against CVE-2026-119077. Reinstalling Quick Page/Post Redirect 5.2.4 is not possible because the plugin is closed. “Expected to become exploited” is Patchstack’s standard wording for high-priority entries, not a report of attacks. The AutomatorWP Pro Webhooks entry, which the notes listed only as a disclosure, carries Patchstack’s exploited marker. The checks for the tampered Quick Page/Post Redirect build were written against the released versions in WordPress.org’s repository. Claims we could not trace to a source, such as specific RHEL package versions and a Wordfence plugin release, are left out.
Common questions about this week’s WordPress security news
AutomatorWP is on the exploited list. Does that include the free plugin?
No. The exploited flaw is in the paid Webhooks add-on, version 1.4.4 and earlier, and only through a webhook that identifies the user by ID. Patchstack lists smaller fixes for the free AutomatorWP plugin this month as well, so update it too, but it is not the exploited entry.
Should I set WP_SECRETS_KEY now?
On staging, yes, to test 7.2. In production, wait for the final release on 8 December and for your host’s guidance. The API is still under discussion, and the key has to be stored and backed up so that it survives a server rebuild.
Do I need to act on the OpenSSL advisory?
Not today. All five issues are low severity, and mostly in QUIC and AES-GCM-SIV, which ordinary WordPress hosting does not use. Install the distribution updates after the 1 December releases, and restart the services that use OpenSSL.
Choose the response path
The week to 16 November left something to check: choose the response path.
The servers under the sites
Get Apache, HTTP/2 and the rest of the web stack checked on every host.
Best when several servers need the Apache version, the protocols per virtual host and the backported packages verified from the running process, the look-back since 11 November done once, and a written result per host.
Get the finding classified and the site restored to a trusted state.
Best when a file-upload plugin left PHP in uploads, wp-config.php went missing, the tampered Quick Page/Post Redirect build turned up, or an account changed hands, and you want every layer removed in one pass.