WordPress Core - Security Vulnerability (CVE-2018-10101)
CVE-2018-10101
Before WordPress 4.9.5, the URL validator assumed URLs with the hostname localhost were on the same host as the WordPress server.
CVE-2018-10101
CVE-2018-10101
Before WordPress 4.9.5, the URL validator assumed URLs with the hostname localhost were on the same host as the WordPress server.
CVE-2018-10101
Machine-generated threat intelligence
AI Updated 1 day ago
AI enriched 1 day ago (2026-09-17 03:05 UTC)
Before WordPress 4.9.5, the URL validator assumed URLs with the hostname localhost were on the same host as the WordPress server.
Severity is MEDIUM (CVSS 6.1). Depending on deployment context, affected components may be exposed to unauthorized actions or data integrity risk.
Exploitability is assessed as Medium based on published exploit references.
Primary risk drivers: published exploit references
Validate affected product versions, prioritize patching, and monitor references for vendor remediation guidance. If immediate patching is not possible, apply compensating controls and limit exposure of vulnerable surfaces.
Track authentication anomalies, unexpected file writes, and suspicious plugin API activity around affected components.
AI risk score 67/100 (Elevated, Medium) with priority P3 Priority. Prioritize remediation where affected components process customer data, admin sessions, or Internet-exposed workflows.
Patch on your next cycle Worth fixing, but not ahead of other work.
Update WordPress Core to 4.9.5 or later.
That is the complete fix. Everything below is what protects you in the meantime.
No Hack Halt control meaningfully contains this one — updating is the remedy. We would rather say so than sell you something that will not help.
Scan your site to see whether it runs WordPress Core, and at which version.
Free, no installation, no account. It reads what your site already publishes, then tells you which plugins carry known vulnerabilities and what to do about each one.
You are affected if your site runs WordPress Core. Versions below 4.9.5 are vulnerable; that release and later are not.
Update WordPress Core to version 4.9.5 or later. That is the complete fix.