Vulnerability · CVE-2026-18072
CVE-2026-18072 is listed by Protect The Shire solves one problem, but risks making another worse.
Published Jul 30, 2026 · WordPress WordPress
Check if you run it
No confirmed exploitation is on record for CVE-2026-18072. EPSS is 2.98%. Act only if a listed version of WordPress WordPress is installed.
Gaps on this record
- No version range is stored. A customer cannot check an installed version against this record.
- No vendor fix or required action is stored. Compare the linked advisory before you change production.
- Severity
- Unknown—
- Known exploitation
- Not in CISA/VulnCheck KEV
- EPSS
- 2.98%
- Remediation
- Not established
- Affected products
- WordPress WordPress
CVE-2026-18072 is listed by Protect The Shire solves one problem, but risks making another worse.
No affected version ranges are stored yet. Use the vendor advisory before you decide this record does not apply.
How to fix CVE-2026-18072
Recommended remediation
No required-action text, fix commit, or clear fixed-version range is stored yet.
Official advisories
What to do
Three questions, each answered from this record only. Confirm the vendor advisory before you patch.
Should you patch?
No confirmed exploitation is on record for CVE-2026-18072. EPSS is 2.98%. Act only if a listed version of WordPress WordPress is installed.
Which versions are affected?
Affected version ranges are not on this record. Compare the installed version with the linked vendor advisory before you change production.
What should an analyst verify?
No weakness class is stored. EPSS 2.98%. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.
Technology hubs
Code
The project this record applies to. Exploit listings stay in References.
No public source repository is identified for this product.
Timeline
Detection, updates, and resolution for this record.
Jul 30, 2026 · Patchstack Database
Detected
CVE-2026-18072 is listed by Protect The Shire solves one problem, but risks making another worse.
Sources
- CVE.orgVulnerability recordCVE-2026-18072
Official CVE identifier
cve.org - FIRST EPSSExploitation probabilityCVE-2026-18072
30-day exploitation probability 3.0%
first.org - Patchstack DatabaseVendor advisoryCVE-2026-18072
We looked at the data: what WordPress.org’s 24-hour update delay means for vulnerabilities and supply-chain attacks. WordPress.org’s new update-review policy – Protect the Shire – is doing exactly what it was built to do – for one kind of threat. For another, it’s quietly making
patchstack.com
Freshness
Last verified in this catalog Oct 18, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.