LiveActive security incident?Get immediate response
CVE Record

CVE-2019-16220: In WordPress before 5.2.3, validation and sanitization of a URL in wp_validate_redirect in wp-includes/plug...

In WordPress before 5.2.3, validation and sanitization of a URL in wp_validate_redirect in wp-includes/pluggable.php could lead to an open redirect if a provided URL path does not start with a forward slash.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2019-16220 is an open redirect issue in WordPress before 5.2.3. A crafted redirect URL could make a trusted WordPress site send users to another location. This is usually more useful for phishing and trust abuse than direct server compromise, but public-facing sites should still be upgraded.

Executive priority

Treat as a routine but necessary web hygiene fix. Prioritize internet-facing WordPress sites, especially those used for customer login, brand communications, or email-linked workflows where redirect trust matters.

Technical view

The issue is in WordPress core's wp_validate_redirect function in wp-includes/pluggable.php. The CVE description says insufficient URL validation and sanitization could allow open redirect behavior when a supplied URL path does not start with a forward slash. WordPress addressed it in the 5.2.3 security release.

Likely exposure

Exposure is most likely on WordPress installations running versions before 5.2.3. Debian-packaged WordPress deployments also received security advisories, so package-managed servers should verify their distribution update status.

Exploitation context

The source bundle does not show CISA KEV listing or confirmed active exploitation. Public references include WordPress, Debian advisories, code changes, WPVulnDB, and later commentary, indicating the issue is publicly documented.

Researcher notes

Evidence supports WordPress core before 5.2.3 as affected. The bundle provides no CVSS, CWE, or confirmed exploitation. Analysis should stay focused on open redirect risk and the vendor's wp_validate_redirect fix path.

Mitigation direction

  • Upgrade WordPress core to version 5.2.3 or later.
  • Apply Debian WordPress security updates where WordPress is package-managed.
  • Check vendor guidance before using workarounds instead of upgrading.
  • Review redirects used in authentication, login, and campaign flows.

Validation and detection

  • Inventory public WordPress sites and record core versions.
  • Confirm wp-includes/pluggable.php includes the vendor fix.
  • Check Debian package versions against DLA 1960-1 or DSA 4599 guidance.
  • Review logs for unusual outbound redirect destinations.
Prepared
Confidence
high
Sources
7

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2019-16220 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
0Timeline events
0ADP providers
10Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.