Report for IP: 137.23.10.39

This IP probed the WordPress ?author= parameter to enumerate valid usernames (e.g. ?author=1, ?author=2). Harvested usernames are then fed into credential stuffing or password brute-force attacks. This is purely reconnaissance — there is no legitimate reason to systematically probe author IDs.

• FireHOL level2 — FireHOL level2 lists addresses seen attacking in the last 48 hours across many sensors. It is large and volatile: addresses enter and leave quickly, so on its own this is weaker, recent-activity evidence.
• This site (WordPress attackers, 90 days) — This site's own data: an IP that attacked WordPress sites and was reported here within the last 90 days. Independent of the third-party lists above.

Several independent community lists agree on this address.

This IP attempted the "wp2shell" exploit chain (CVE-2026-63030 / CVE-2026-60137) — a WordPress core REST API vulnerability where the /batch/v1 endpoint's route dispatch can be confused into bypassing authentication, then chained with a SQL injection for unauthenticated remote code execution. Publicly weaponized since July 2026 with automated exploit toolkits circulating on GitHub. Patched in WordPress core 7.0.2 and 6.9.5 — any unpatched site remains fully exposed to this pre-auth RCE.

This IP attempted CVE-2026-76581, a critical (CVSS 9.8) unauthenticated admin-takeover vulnerability in WPMU DEV Dashboard's Hub SSO feature — a signature-verification flaw lets an attacker forge a valid SSO token and gain full administrator access without credentials. Actively, automatically mass-scanned for across the internet.

This IP was blocked attempting to log into a WordPress site's wp-login.php — either from a disallowed country or after exceeding the allowed number of failed login attempts. Automated credential-stuffing and brute-force tools account for the overwhelming majority of this traffic; legitimate users rarely trigger a hard IP block on login alone.