Infosec Archivecodegen.work

WordPress, TP-Link, Synology & PHP Threat Report

Two actively exploited flaws in CISA KEV (WordPress core update RCE and PHP2Shell), C3RB3R ransomware hitting outdated Synology DSM, eight critical WordPress plugin bugs, and high-severity TP-Link router and Tapo fixes.

Published Coverage 27 Oct – 10 November 2026 WordPressTP-LinkSynologyPHP
Priority items
5
Actively exploited
3
In CISA KEV
2
Critical (CVSS ≥ 9)
3
CVEs referenced
26

Executive summary

The items below need action now, in priority order.

  1. 1

    PHP2Shell: unauthenticated RCE in PHP core

    CVSS 9.2 · Critical
    PHPExploited in the wildCISA KEV

    Do now: Upgrade to PHP 8.5.12, 8.4.27, 8.3.36 or 8.2.35, then restart every PHP worker.

    CVE-2026-109618 CVE-2026-109619

  2. 2

    WordPress core RCE during the update process

    CVSS 8.1 · High
    WordPressExploited in the wildCISA KEV

    Do now: Block web access to wp-content/upgrade/, then update to 7.1.4 or your branch backport.

    CVE-2026-119977

  3. 3

    Eight critical WordPress plugin flaws

    CVSS 10.0 · Critical
    WordPressUnauthenticated

    Do now: Inventory plugins. Update, or deactivate where no fixed version exists.

    CVE-2026-94169 CVE-2026-104798 CVE-2026-103768 CVE-2026-109219 CVE-2026-89079 CVE-2026-109515 CVE-2026-104730 CVE-2026-94388

  4. 4

    C3RB3R ransomware targeting outdated Synology DSM

    CVSS 9.8 · Critical
    SynologyExploited in the wildRansomware

    Do now: Update DSM to the fixed builds below and turn on automatic updates.

    CVE-2026-13684 CVE-2026-13639 CVE-2024-10441

  5. 5

    TP-Link RE305 root command execution and Tapo Cloud flaws

    CVSS 8.7 · High
    TP-LinkPatch available

    Do now: Update RE305 V3 and Archer C7 V5 firmware. Tapo Cloud was fixed server-side.

    CVE-2026-102814 CVE-2026-105821 CVE-2026-105822

WordPress

Core: CVE-2026-119977, exploited and in CISA KEV

WordPress 7.1.4 shipped on October 28 with 22 fixes. Most are stored XSS bugs that need a Contributor account or higher. The exception is an unauthenticated remote code execution flaw in the core update process, found by Umut Bayram and tracked as CVE-2026-119977. Wordfence scores it CVSS 8.1; WordPress's own advisory rates it low. CISA added it to the Known Exploited Vulnerabilities catalog in early November with a short remediation deadline (reported as November 6).

How it works. The old updater extracted packages into a predictably named folder that was reachable over the web. An attacker who timed a request during an update could run a rogue WordPress installer against their own database and execute PHP as the web server user. Version 7.1.4 randomizes the folder name and keeps the folder's index file in place. The catch: the update to 7.1.4 still runs the old updater, so a site can be exposed one last time during that update.

Exploitation. Wordfence saw attack attempts nine minutes after deploying its firewall rule on release day and has blocked more than 240,000 requests. Some sources polled small groups of sites for hours, consistent with trying to catch the moment of update. Public exploit code has been on GitHub since late October.

Affected: 4.7 through 7.1.3. Fixed: 7.1.4, with backports to every branch down to 4.7.39. Versions 4.6 and older get no fix.

Indicators of compromise: requests to PHP files under wp-content/upgrade, unknown administrator accounts, unfamiliar plugins, and PHP files in wp-content/upgrade that nobody placed there.

Plugins: eight critical vulnerabilities (disclosed November 3)

None is reported as exploited yet, but all are high impact and most need no authentication.

Plugin CVE CVSS Issue Affected
The Grid CVE-2026-94169 10.0 Remote code execution ≤ 2.8.1
My Calendar CVE-2026-104798 9.8 Unauthenticated privilege escalation ≤ 3.8.7
ELEX HelpDesk & Customer Ticketing CVE-2026-103768 9.8 Arbitrary file upload via IMAP attachments ≤ 3.3.7
Mang Board CVE-2026-109219 9.8 Arbitrary file upload ≤ 2.4.4
Theme My Login CVE-2026-89079 9.8 Unauthenticated privilege escalation ≤ 7.2.1
MailOptin CVE-2026-109515 9.8 Unauthenticated privilege escalation ≈ 1.2.7.x (verify)
Sunshine Photo Cart CVE-2026-104730 9.8 PHP object injection ≤ 3.7.4
Green Popups CVE-2026-94388 9.3 SQL injection fixed in 7.6.3

No in-the-wild exploitation or public proof of concept has been reported for any of the items below.

Tapo Cloud: CVE-2026-105821 and CVE-2026-105822 (updated November 3)

Both score CVSS 8.3 (v4.0). CVE-2026-105821 is broken access control in the Tapo Cloud MQTT proxy: knowing another device's ID was enough to upload content into its owner's cloud storage, where it could show up as a genuine event. CVE-2026-105822 is a server-side request forgery in the same proxy. TP-Link fixed both on the server side; users need to do nothing.

RE305 V3 and Archer C7 V5 (updated October 27; HKCERT bulletin November 5)

  • CVE-2026-102814 (8.7 High), RE305 V3: a weak key in the TDDP protocol lets an attacker on the local network forge packets and run commands as root. The most serious item in this batch.
  • CVE-2026-102815 and CVE-2026-102816 (6.9), RE305 V3: command injection in a root-owned local service.
  • CVE-2026-102813 (6.1), RE305 V3: predictable password-reset code with no lockout.
  • CVE-2026-18330 (6.1) and CVE-2026-102812 (6.9), Archer C7 V5: hardcoded keys that expose the admin password and Wi-Fi credentials.
  • Fixed firmware: Archer C7 V5 1.3.1 Build 20260821; RE305 V3 1.1.8 Build 20260921.

TP-Link's advisory lists CVE-2026-102816 twice with different descriptions, and HKCERT's bulletin adds CVE-2026-89052 and an Archer C6 fix that TP-Link's US page does not mention. Archer C6 owners should check TP-Link's regional advisory (HK FAQ 5356).

Tapo C210 (October 19, older but still relevant)

CVE-2026-105814 (5.3) is an authentication bypass in the camera's local API that allows protected actions, including pan and tilt, without a session. CVE-2026-105815 (7.1) exposes credential material accepted as an admin password. Fixed in firmware V3.6_1.2.7 Build 260818.

Synology

C3RB3R ransomware exploiting outdated DSM

Synology said in late October that attackers are exploiting DSM vulnerabilities on devices that have not been updated, and urged all users on vulnerable versions to update immediately. The campaign is linked to the C3RB3R ransomware, which renames encrypted files with a .L0CK3D extension and drops a read-me3.txt ransom note in each folder.

Synology's statement points to a flaw fixed in December 2024: CVE-2024-10441 (CVSS 9.8, system plugin daemon RCE, advisory SA-24:20). Qihoo 360 reports the group is also using two critical flaws fixed in September 2026 under advisory SA-26:13:

Synology's advisory describes the impact of both as arbitrary file read/write and denial of service. Some third-party write-ups call them root RCE; Synology's text does not say that. No public proof of concept has been reported.

DSM branch Fixed build (SA-26:13)
7.4 7.4-90075
7.3 7.3.2-86009-4
7.2.2 7.2.2-72806-9
7.2.1 7.2.1-69057-12

Devices that have not been updated since 2024 are exposed to CVE-2024-10441 as well. Its fixes are in 7.2.2-72806-1, 7.2.1-69057-6, 7.2-64570-4, 7.1.1-42962-7 and 6.2.4-25556-8.

SA-26:13 also fixes six lower-severity DSM issues (CVSS 2.7 to 8.8), and SA-26:06 (April 2026, details published September) fixes eleven more. Neither has reported exploitation; the same update covers them.

PHP

PHP2Shell: CVE-2026-109618 and CVE-2026-109619

Disclosed and patched on October 21, so slightly older than this report's window, but still under broad exploitation. Both score CVSS 9.2 (v4.0) and come from the same root cause: PHP can leave memory corrupted when a request ends abnormally.

  • CVE-2026-109618: running out of memory aborts a request while its data is half-initialized (for example during multipart upload parsing), and cleanup then frees memory that was never valid.
  • CVE-2026-109619: per-request state outlives its memory, so the next request on the same worker uses freed memory. Session upload progress, enabled by default, is one confirmed trigger.

Affected: any PHP serving web requests, including PHP-FPM, Apache mod_php, php-cgi, FrankenPHP and LiteSpeed. Fixed in 8.5.12, 8.4.27, 8.3.36 and 8.2.35. PHP 7.4 to 8.1 got source-level backports only, with no official builds, and 7.3 and older get nothing.

Exploitation. Amazon saw an attempt on its honeypots on October 17, four days before disclosure. Cloudflare and watchTowr saw attacks from October 21. CISA added both CVEs to KEV around October 26. Researchers confirmed working exploits against WordPress, Drupal, Joomla, Magento, MediaWiki, Laravel, Symfony and phpBB. One unconfirmed report describes PHP2Shell chained with a Linux kernel bug to get root on about two dozen internet-facing firewalls.

Is the patch complete? Claims that RCE survives on 8.5.12 came from a single self-published source and are unconfirmed. One related bug, php-src #24488, is real but causes a crash only, and its fix lands in 8.4.28 and 8.5.13. A separate, narrower flaw, CVE-2026-115560, affects only unusual session configurations and is mitigated by disabling session upload progress.

Sources