HANECSReguFrame
WORDPRESS CORE / SECURITY CHECK

Check WordPress.
Without false reassurance.

Detect public WordPress signals or compare the known core release from your dashboard with current official advisories.

Information reviewed 26 October 2026 · Reference: WordPress 7.1.3

CVE-2026-63030 · GHSA-52p2 · GHSA-7hp8

A visible WordPress signal does not prove the patch level. No visible signal does not rule out WordPress. Plugins, themes, hosting backports and possible compromise are not assessed.

FREE / NO REGISTRATION

WordPress Security Check

Domain detection remains passive. For reliable version classification, use the release shown under Dashboard → Updates.

Public home page only

The domain is sent to our server. At most 256 KiB of the public home page; no exploits, logins, uploads, plugin enumeration or port scans. Privacy information for the check

I already know my WordPress version

The version comparison runs locally in your browser and does not send this entry to the checking service.

OFFICIAL SOURCES / IN CONTEXT

What this check considers

CVE-2026-63030

REST API batch-route confusion and SQL injection leading to RCE

Affected branches and fixed releases are included in the local version comparison.

Original source ↗
GHSA-52p2-r8wf-jcrf

Pre-auth reflected XSS on the login screen

Affected branches and fixed releases are included in the local version comparison.

Original source ↗
GHSA-7hp8-65ch-5whp

Unauthenticated path traversal leading to conditional RCE

Affected branches and fixed releases are included in the local version comparison.

Original source ↗
06 OCT 2026

WordPress 7.1.3

The security and maintenance release of 6 October 2026 contains seven security fixes. WordPress recommends updating immediately.

Original source ↗

What the domain check cannot do

A visible WordPress signal does not prove the patch level. No visible signal does not rule out WordPress. Plugins, themes, hosting backports and possible compromise are not assessed.

A sound sequence for operators

  1. Confirm the version in the dashboard.
  2. Create a verified backup and test restoration.
  3. Update core, plugins and themes.
  4. For a match, have logs, administrator accounts and unexpected files reviewed.

Sources and information date

Initial technical orientation by HANECS. Not a penetration test, security certificate or automatically updated service.

HANECS / TECHNICAL CLASSIFICATION

A match or an unclear version?

HANECS can help classify the technical finding, document the patch level and establish a traceable security process.

Discuss the finding ↗