BoletimSec•September 23, 2026•🇵🇹Translated from Portuguese

WordPress Patches Critical Core Vulnerability CVE-2026-87902 Affecting All Versions from 4.7.0

WordPress has issued security updates that address a critical vulnerability in the platform's core, identified as CVE-2026-87902 and rated CVSS 9.2. The flaw affects all versions from 4.7.0 to 7.1.1, leaving the vast majority of installations exposed until the latest patches are applied.

The vulnerability exists in the base code rather than in any plugin or theme. This means sites running a clean installation with no additional extensions are still at risk. An attacker can load a PHP file located outside the designated theme directories. Under specific server configurations, this capability can be leveraged to execute arbitrary code chosen by the attacker.

Exploitation requires no authentication and no interaction from any logged-in user, making the attack surface available to any visitor. The absence of required credentials significantly increases the severity of the issue.

Patch Releases

Security updates have been distributed across all currently supported branches:

  • 7.1.x → version 7.1.2
  • 7.0.x → version 7.0.6
  • 6.9.x → version 6.9.9
  • 6.8.x → version 6.8.10
  • 6.7.x → version 6.7.9
  • 6.6.x → version 6.6.9
  • Support extends back to 4.7.37

The vulnerability was reported in July by researcher Robert Ressl via a private disclosure on HackerOne and made public on 22 September. No evidence of active exploitation in the wild has been recorded to date.

Site owners are strongly advised to update immediately and ensure automatic updates remain enabled. For environments where immediate patching is not feasible, temporary mitigations include disabling register_argc_argv and removing unused PEAR components.

Related articles

Security NEXT•Vulnerabilities & Exploits

NICT Warns of A2B Attacks Where Reverse-Engineered Android Apps Expose Vulnerable Backend Servers

Japan's National Institute of Information and Communications Technology (NICT) has issued an alert on A2B attacks, in which publicly available Android apps are reverse-engineered to identify and target their backend servers. The technique, called App-to-Backend Attack, allows threat actors to discover internal server endpoints even when organizations do not publish connection details. Once identified, attackers exploit vulnerabilities, weak authentication, or misconfigured APIs on those servers, leading to unauthorized access and data theft. NICT notes that multiple recent membership-service breaches in Japan stem from this vector rather than flaws in the mobile apps themselves. The institute urges developers and operators to harden backend infrastructure, conduct thorough compromise assessments, and apply proper access controls. Related incidents include unauthorized access to Lawson ID services, Yakiniku King app member data, and Japan Post's postal app.

Habr•Vulnerabilities & Exploits

From HFT to Infosec: How AI Accelerates the Developer-Hacker Arms Race

An experienced security researcher draws a parallel between high-frequency trading evolution and modern vulnerability research, showing how artificial intelligence compresses the time between patch release and working exploit. The author describes the classic workflow where developer Rob fixes buffer overflows in an FTP server while researcher Dave reverse-engineers the diff to locate the exact change. With AI assistance, both sides now generate patches or exploits in minutes rather than days or weeks. The piece highlights that publishing a patch effectively discloses the location of the flaw, allowing automated tools to produce reliable exploits almost instantly. Historical examples such as wu-ftpd CVEs and the EternalBlue/MS17-010 worm illustrate how quickly mass exploitation follows disclosure. The author warns that open-source projects face an existential dilemma: withhold patches and leave users exposed, or release them and trigger immediate automated scanning. Recommendations include mandatory back-porting of fixes and wider use of runtime protections, yet the overall outlook remains pessimistic about the coming wave of fully automated attacks.

Habr•Vulnerabilities & Exploits

Ghost Assets in Vulnerability Management: How Identification, Merging and Asset History Eliminate Anomalies in MaxPatrol VM

Positive Technologies experts explain how infrastructure changes create duplicate, merged and phantom assets that distort vulnerability management. The article details three core mechanisms inside MaxPatrol VM: unique asset identification across scan sources, non-destructive merging of new and existing data, and full lifecycle history with configurable aging policies. It describes how the system distinguishes assets using prioritized keys such as system ID, FQDN, MAC address and VM ID, then applies recursive merging rules that respect multiple data sources. Policies allow teams to set freshness and obsolescence thresholds, automatically hiding assets after 90 days while preserving historical snapshots for PDQL queries. The piece also covers practical cloning and partial-scan scenarios that can produce misleading duplicates or lingering collections.

BoletimSec•Vulnerabilities & Exploits

GreyNoise Detects Active Exploitation Attempts of CVE-2021-36260 Against Hikvision Cameras

GreyNoise recorded exploitation attempts targeting CVE-2021-36260 in Hikvision cameras and recorders between September 21 and October 1. The vulnerability carries a CVSS score of 9.8 and allows unauthenticated remote command execution through insufficient input validation in the embedded web server. Attack traffic originated from four IP addresses, three routed through a commercial VPN in Lithuania and one from a Ukrainian residential network, with all targets located in Ukraine. Attackers leveraged a publicly available Nuclei template to probe devices, though GreyNoise confirmed only scanning activity and not successful compromises. The five-year-old flaw remains actively scanned despite an available firmware patch from Hikvision and a CISA advisory recommending immediate updates. Password changes provide no protection because the attack requires no authentication. Defenders are advised to apply firmware updates, remove devices from public internet exposure, and segment video surveillance networks from critical infrastructure.