tag

WordPress

8 articles with this tag

2026-11-02

WordPress 7.1.4 flaw CVE-2026-119977: a core-update race that can lead to remote code execution is fixed; check your version and auto-updates

On October 28, 2026, the WordPress project released security release 7.1.4, which fixes a flaw in the core update process that can lead to remote code execution. According to WordPress's GitHub advisory, during a core update that uses a complete package, WordPress extracted the new files to a predictable directory inside the web-served upgrade folder, and an unauthenticated attacker who wins a race against that extraction could reach remote code execution (RCE). The fix ships in 7.1.4 and is backported to every branch back to 4.7 (7.0.8, 6.9.11, 6.8.12 and so on). CVE-2026-119977 was published on October 31 by Wordfence as the CNA, rated CVSS v3.1 8.1 (High) with attack complexity High; WordPress's advisory rates it Low and gives no score. According to SecurityWeek, a WordPress security vendor saw its first firewall-rule match nine minutes after deploying the rule and logged more than 18,500 requests aimed at temporary update locations in the first 21 hours; the vendor has reported no successful compromise. CISA added the CVE to its Known Exploited Vulnerabilities (KEV) catalog on November 3 (the KEV entry gives US federal agencies a November 6 due date, and CISA requires them to do a forensics triage under BOD 26-04 as well as patch). Sites with automatic background updates should update on their own; sites with auto-updates off should update manually from the Updates screen. This site's conclusion: treat it as exploited, update today, and if your update was late, check for signs of compromise (this site's advice).

2026-10-21

[Breaking] PHP flaws CVE-2026-109618 and CVE-2026-109619 now exploited, added to CISA's KEV catalog: update to 8.5.12, 8.4.27, 8.3.36 or 8.2.35 now

On October 21, 2026, the PHP security team released PHP 8.5.12, 8.4.27, 8.3.36 and 8.2.35, fixing two critical vulnerabilities that can allow unauthenticated remote code execution (RCE), and urged all users to update immediately. CVE-2026-109618 involves out-of-memory handling and CVE-2026-109619 involves stale internal state surviving between requests; both are rated 9.2 under CVSS v4.0. All PHP installations serving web requests are at risk (PHP-FPM, Apache mod_php, php-cgi, FrankenPHP, LiteSpeed). The team considers mod_php the highest risk, citing a demonstrated exploit in which an unauthenticated request triggers the attack before any application code runs. PHP 8.1 and older get no official update; the team provided minimal source backports for 7.4, 8.0 and 8.1. Linux distributions received the patches in advance. There is no complete mitigation; updating is the only safe choice. On October 22, Japan's IPA and JPCERT/CC issued alerts and JVN published JVNVU#99905564. CISA, which had not observed exploitation when it first published its alert, added both flaws to its Known Exploited Vulnerabilities (KEV) catalog on October 26, with an October 29 deadline for US federal civilian agencies. According to media reports, a security researcher's honeypots running unpatched PHP 8.4.26 under mod_php saw successful remote code execution on October 24. A major cloud provider's honeypots had seen exploitation attempts from October 17, four days before disclosure. As far as this site could find, no break-in outside honeypots had been made public as of October 27. Most major Japanese shared-hosting providers have announced that the fix is applied, but some, such as KAGOYA, have not. On October 23, the PHP team disclosed a third issue (CVE-2026-115560) that the October 21 releases do not fix. It can lead to code execution only under a specific combination of configuration and application code; the team calls it unlikely in practice, will ship the fix and a full advisory with the next regular release, and recommends setting session.upload_progress.enabled=0 until then. Affected versions and a CVSS score have not been published, and no exploitation has been reported. As of October 29 (checked on php.net), no fixed release for this issue was out. On October 28, CISA also added the Linux kernel flaw CVE-2026-46300 to KEV (October 31 deadline for US federal agencies) and said it can be chained with these two flaws to implant PHP webshells and run commands as root. This site's take: exploitation is now confirmed, so confirm whether you or your provider updates PHP for each site and move to the fixed version today. Also check logs from October 17 onward for signs of a break-in. On shared hosting, check your provider's completion notice on its official website.

2026-10-20

Rank Math PRO 3.0.123 Shipped with Malware (October 2026): Who Is Affected and What WordPress Site Owners Should Do

On October 16, 2026 (UTC), Rank Math announced that Rank Math PRO v3.0.123, the paid version of its WordPress plugin, contained malware for a limited number of users who downloaded it between 20:02 UTC on October 15 and 07:12 UTC on October 16. The malware could compromise a site if the plugin was activated, and could recreate its hidden backdoor whenever the site was visited. The company removed the affected files and released a clean v3.0.124. The free version distributed on WordPress.org is not affected. Neither the number of affected users nor how the malware got into the files has been disclosed. As of October 20, the last change to the notice was on October 19, when a note that the free version is not affected was added. This site's conclusion: treat any site that activated a copy of 3.0.123 obtained during the affected window as compromised, and either restore from a backup taken before the window or delete the whole plugin folder and clean up in the order the company gives. Either way, change every credential the site could read.

2026-10-15

Unauthorized Access to Some ConoHa WING (GMO Internet) Web Servers (426 Accounts): Data in Customers' Web Server Areas Affected, and What Site Owners Should Do Today

On September 20, 2026, GMO Internet, Inc. announced that on some hosting servers (web servers) of its ConoHa WING rental hosting service, a third party had gained unauthorized access to the web server areas of some customers and installed a malicious program. 426 accounts are affected, and the data concerned is 'data stored in customers' web server areas'. The access and installation began on September 3; the company detected it on September 16, and on September 18 identified the cause and scope and removed the programs. It says it has identified the cause but has not disclosed it. Member, contract and payment data are managed in a separate environment and were not leaked, it says. The notice does not say whether data in the web server areas was taken. Affected customers were contacted individually at their registered email address, and customers who were not contacted are not affected. There was no follow-up notice as of October 15. This site's take: first check whether you received an individual email and, if so, follow its instructions. Then treat the credentials kept in your web server area (the database password in wp-config.php, API keys in .env and so on) as read and change them, and look for files, administrators and scheduled jobs added since September 3.

2026-10-11

How to check if your website or server was hacked: step-by-step checks for shared hosting, WordPress and a VPS, and what to do first if you find something

Checking a site for intrusion means looking at both the signs visible from outside and the traces left inside. Signs: Search Console's Security issues report, a 'This site may be hacked' label in search, a notice from your host, unknown admins, redirects that happen only on mobile or from search. Traces: admin users, modified core files (wp core verify-checksums), login history, authorized_keys, cron, listening ports, recently changed files. This site's view: finding nothing does not prove you are clean. If you do find something, preserve evidence before cleaning, rotate every credential from a clean device, restore from a pre-intrusion backup or rebuild, close the entry point, and only then request a review.

CriticalCVSS8.12026-09-26

CVE-2026-87902 — Unauthenticated file inclusion in WordPress core (conditional RCE): explainer and fix

Unauthenticated local file inclusion in WordPress core 4.7–7.1.1 (CWE-98), leading to RCE when theme and server conditions line up. Fixed 22 September (7.1.2 and every branch back to 4.7); CISA added it to KEV on 25 September. This site's view: an EPSS of 3% does not matter once it is in KEV. Update, and also turn off PHP's register_argc_argv to remove the server-side condition RCE needs.

CriticalCVSS9.82026-07-21

CVE-2026-63030 / CVE-2026-60137 — Unauthenticated SQLi to RCE in WordPress core (explainer & fixes)

A REST API batch-endpoint route-confusion flaw in WordPress core (CVE-2026-63030, CWE-436) chains with the WP_Query author__not_in SQL injection (CVE-2026-60137, CWE-89) to reach unauthenticated SQLi → RCE (CVSS 9.8, in CISA KEV). The 6.9/7.0 backports fix both; 6.8.6 fixes 60137 only. The main fix is updating core to 6.8.6 / 6.9.5 / 7.0.2, plus a compromise check. WordPress is core software with an enormous install base, so updating is the top priority.

2026-07-02

WordPress security — a production hardening reference

WordPress has the largest share, so it's the biggest target, but the ways in are predictable (plugin/theme vulnerabilities, skipped updates, weak admins, exposed admin panels). This is a working reference: (1) a priority-ordered hardening checklist (P0–P2), (2) per-area guidance — automatic updates, minimizing plugins/themes, strong admin + 2FA, reducing admin exposure (xmlrpc/REST enumeration/file editing), wp-config and secrets, file permissions, HTTPS/backups, PHP/dependency updates, and (3) a self-verification checklist. Defensive only — no attack steps.