WordPress 7.1.5 Released to Patch Multiple Vulnerabilities Including Privilege Escalation
The WordPress development team has released WordPress 7.1.5, a security update that resolves multiple vulnerabilities and strengthens overall platform protections. Site administrators are urged to apply the patch without delay.
Published on November 18, 2026, the release contains approximately 20 fixes focused on vulnerability remediation and security hardening. Among the most critical changes is a patch for a privilege-escalation flaw in the Template Part block. Attackers could exploit block attributes to elevate permissions, potentially leading to remote code execution on affected sites.
Another high-impact issue corrected in multisite configurations allowed a site administrator to abuse the customizer menu preview function and seize control of a super-administrator account. The update also addresses two separate SQL injection vulnerabilities and several instances of cross-site scripting (XSS), in addition to various information-disclosure problems.
WordPress installations with automatic background updates enabled will receive the new version automatically. Administrators may also apply the update manually from the dashboard. Backports of the fixes are being prepared for all branches beginning with WordPress 4.7.
Related articles
PHP Prepares Critical Patches for All Supported Versions One Month After Emergency Update
The PHP development team announced on November 18 that it will release updates for all supported interpreter versions to address multiple vulnerabilities, including critical ones. The fixes target a use-after-free flaw in file upload progress tracking that can lead to remote code execution when specific session serialization formats are combined. This comes shortly after emergency patches issued on October 21 resolved two remote code execution issues collectively known as PHP2Shell. The new vulnerability, tracked as CVE-2026-115560 with a CVSS score of 9.8, arises when applications switch session formats from php_binary or php_serialize to php after upload tracking has begun. Developers are advised to disable session.upload_progress.enabled until patches are applied and verified. Releases are scheduled for November 19 between 17:00 and 17:30 Moscow time, accompanied by a detailed security bulletin.
CISA Adds Four Actively Exploited Vulnerabilities to KEV Catalog Targeting Apache Axis, REDCap, Synology DSM and LiteLLM
The U.S. Cybersecurity and Infrastructure Security Agency has added four vulnerabilities to its Known Exploited Vulnerabilities catalog after confirming active exploitation in the wild. The flaws affect Apache Axis, REDCap, Synology DSM, and LiteLLM, prompting mandatory remediation for federal agencies. CVE-2026-90436 in Apache Axis allows unauthenticated remote code execution via crafted SOAP fault messages under specific conditions. CVE-2026-90817 in REDCap enables unauthenticated remote code execution through manipulated HTTP requests targeting public survey and data import functions, provided an attacker knows a valid survey hash. The remaining two vulnerabilities in Synology DSM and LiteLLM were also confirmed exploited but lack detailed public descriptions at this time. Organizations are urged to apply patches immediately to prevent further attacks.
NGINX Patches Critical Remote Code Execution Vulnerability Present Since 2015 (CVE-2026-123007)
NGINX has released patches for a critical vulnerability, CVE-2026-123007, that allowed unauthenticated remote code execution on servers with HTTP/2 enabled. The flaw existed in the codebase since version 1.9.5 released in 2015 and was fixed in versions 1.30.7 and 1.31.9 on November 18. Researchers at Wiz discovered that improper handling of HTTP/2 flow control counters leads to memory corruption, enabling code execution that bypasses ASLR and runs with the privileges of the NGINX worker process. The vulnerability affects even servers serving only static files without backend application connections. A second related issue, CVE-2026-123633, involving use-after-free in HTTP/2 handling, was also addressed in the same updates. Administrators are advised to apply the patches immediately or disable HTTP/2 as a temporary mitigation if updates cannot be installed promptly. No in-the-wild exploitation of CVE-2026-123007 had been observed at the time of disclosure.
Managing Bug Bounty Programs: Handling Report Overload, Duplicates, and AI-Generated Submissions
Launching a bug bounty program is only the beginning; the real challenge lies in managing the influx of reports, filtering duplicates and AI-generated noise, and ensuring vulnerabilities are actually fixed. Standoff Bug Bounty recommends starting with private programs limited to 30-50 researchers to build internal processes before scaling. Companies like Flavau developed custom DevSecOps consoles that cut report triage time by a factor of 10 by automating duplicate detection and assignee assignment. The platform introduced neural slop windows that limit submissions based on researcher quality history, addressing the surge in AI-generated invalid reports observed in spring 2026. Fixed response timelines, clear ownership roles, and prioritized remediation of critical issues help maintain program effectiveness. Google’s decision to pause its OSS VRP in October 2026 due to automated report floods highlights broader industry concerns, yet experts maintain that human-driven independent validation remains essential. Key success metrics include reduced risk from fixed high-severity issues, lower average payout costs, and improved cross-team communication between security and development.