Evidence used
- CISA confirms exploitation in the wild.
- The selected CVSS metric records a network-reachable, unauthenticated path with no user interaction.
- EPSS is 10.12% for the current model date.
BlackTreeCVE IntelligenceFull vulnerability report · 2026
CVE-2026-63030High confidence
WordPress Core Interpretation Conflict Vulnerability
WordPress · Core
Official source article: GitHub GHSA-FF9F-JF42-662Q ↗. Check the applicable product and release in the original source.
9.8CriticalCVSS 3.1
Mitigate now
Mitigation availableCISA confirms exploitation in the wild and lists 2026-07-24 as the remediation due date.
R
Open reassessment dashboard →Operational reassessment
Published severity in operational context
Published severityCritical→Operational priority:Critical, unchanged from published severity.unchanged
Compensating controls
- Apply the linked authoritative mitigation while planning the permanent fix.
- Restrict the affected network interface to trusted sources where business-safe.
- Increase monitoring for the attack path and post-exploitation behaviour described in the report.
Verification
- Confirm that the asset runs WordPress Core and falls inside the recorded affected range.
- Recheck the vendor advisory before scheduling a change because no verified fixed version is currently retained.
- Validate exposure, authentication requirements and compensating controls in the actual environment.
- Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Distribution package intelligence
5 package statesRelease-specific package status
Debian, ubuntu findings are scoped to the named distribution, release and source package. An absent finding does not mean a package is unaffected.
Repository candidate not checked
A published vendor fix does not prove that a matching update is enabled and installable on a particular asset. Confirm the local package candidate before scheduling remediation.
| Distribution release | Source package | Vendor state | Fixed version | Evidence |
|---|---|---|---|---|
| Debian trixietrixie · source | wordpress | Not affectedDebian marks this release not affected (fixed-version marker 0). | Not published in this feed | Debian Security Tracker ↗Source updated 6 Oct 2026 |
| Debian bookwormbookworm · source | wordpress | Not affectedDebian marks this release not affected (fixed-version marker 0). | Not published in this feed | Debian Security Tracker ↗Source updated 6 Oct 2026 |
| Debian forkyforky · source | wordpress | Vendor fix publishedDebian records a fixed source-package version for this release. | 7.0.2+dfsg1-1 | Debian Security Tracker ↗Source updated 6 Oct 2026 |
| Debian sidsid · source | wordpress | Vendor fix publishedDebian records a fixed source-package version for this release. | 7.0.2+dfsg1-1 | Debian Security Tracker ↗Source updated 6 Oct 2026 |
| Ubuntu 24.04 LTSnoble · standard archive | wordpress | Under evaluationCanonical reports that the package might be affected and still needs evaluation or fixing. | Not published in this feed | Canonical Ubuntu Security ↗Source updated 5 Oct 2026 |
CISA confirms exploitation in the wild and lists 2026-07-24 as the remediation due date.
Mitigation available01
What, why and how
WordPress Core contains an interpretation conflict vulnerability that could allow an attacker to perform SQL Injection and achieve Remote Code Execution. This vulnerability can be chained with CVE-2026-60137.
What
WordPress Core contains an interpretation conflict vulnerability that could allow an attacker to perform SQL Injection and achieve Remote Code Execution. This vulnerability can be chained with CVE-2026-60137.
Why
Product A handles inputs or steps differently than Product B, which causes A to perform incorrect actions based on its perception of B's state.
How
An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may execute code or commands in the affected security context.
What
WordPress Core contains an interpretation conflict vulnerability that could allow an attacker to perform SQL Injection and achieve Remote Code Execution. This vulnerability can be chained with CVE-2026-60137.
Why
Product A handles inputs or steps differently than Product B, which causes A to perform incorrect actions based on its perception of B's state.
How
An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may execute code or commands in the affected security context.
02
Exploit reality and attack path
CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.
Observed exploitation Confirmed in the wild
?
Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.CISA added this CVE to its Known Exploited Vulnerabilities catalogue on 2026-07-21.
Public PoC / exploit material None recorded
?
Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.
- Likely attack path
- a network path → Interpretation Conflict → execute code or commands in the affected security context
- Attack surface
- Network
- Privileges required
- None: unauthenticated exploitation is possible
- User interaction
- None
- Attack complexity
- Low: no specialised conditions are recorded
- Security boundary
- Unchanged: impact remains within the vulnerable component's security authority
- Weakness
?
CWE means Common Weakness Enumeration: a standard category for the underlying weakness. - CWE-436 ↗
CWE-436: Interpretation Conflict. Product A handles inputs or steps differently than Product B, which causes A to perform incorrect actions based on its perception of B's state.
- CVSS vector
?
CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity. CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HCommon Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.
AVNetworkAttack vector: The vulnerable component can be reached over a network.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRNonePrivileges required: The attacker does not need an account or existing privileges.UINoneUser interaction: No action by another user is required.SUnchangedScope: The security impact remains within the vulnerable component's authority.CHighConfidentiality impact: A successful attack can cause a major loss.IHighIntegrity impact: A successful attack can cause a major loss.AHighAvailability impact: A successful attack can cause a major loss.- Post-exploitation / living off the land
- After compromise, an attacker may use built-in shells, scripting engines, scheduled tasks and native network utilities for discovery, persistence or movement. This is a plausible LoTL path, not evidence that it has occurred for every attack.
03
Patch and workaround
Operational remediation based on structured source evidence.
- Status
?
Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change. - Mitigation available
- Action
- The Cyber Centre encourages users and administrators to review the provided web links and apply the necessary updates.
- Workaround
- No verified workaround is recorded. If business-safe, reduce exposure to the affected interface and allow only trusted sources until authoritative guidance is available.
Official vendor articles1 stored document
Linked articles are downloaded and versioned as source evidence. A CVE mention or approved update relationship does not, by itself, verify a fix for every product branch.
- WordPress 7.0.2 Release – WordPress News →Original publisher ↗Searchable text snapshot · Captured 26 Sep 2026WordPress 7.0.2 is now available. The 7.0.2 security release addresses one critical and one high severity security issue. Because this is a security release, it is recommended that you update your sites immediately. Due to the severity, the WordPress.org team have enabled forced updates via the auto-update system for s
04
Evidence and provenance
Published 17 Jul 2026 · Last source change 22 Jul 2026, 03:55 UTC · CWE-436 · Interpretation Conflict
CVE recordCVE.org · 5.2
CVSS sourceCNA
EPSS source FIRST · tracked since 2026-08-14
?
The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.European sourceENISA EUVD · EUVD-2026-45280
Product sourceCISA KEV
Remediation sourceCVE/CNA references
CWE sourceCNA
NVD statusNVD enriched
Core structured fields are present and their contributing authorities are shown above.
Material change intelligence
View recent updates ↗What changed after publication
- BlackTree coverageBlackTree article coverage changed from 1 BlackTree article to 2 BlackTree articles.BlackTree editorial ↗
- Before
- 1 BlackTree article
- After
- 2 BlackTree articles
- BlackTree coverageBlackTree article coverage changed from no BlackTree article to 1 BlackTree article.BlackTree editorial ↗
- Before
- no BlackTree article
- After
- 1 BlackTree article
- Vendor guidanceAuthoritative vendor guidance changed: removed remediation: cyber.gc.ca/wordpress-security-advisory-av26-723.contact@wpscan.com ↗
- Before
- remediation: cyber.gc.ca/wordpress-security-advisory-av26-723 · vendor advisory: github.com/GHSA-ff9f-jf42-662q
- After
- vendor advisory: github.com/GHSA-ff9f-jf42-662q
- Remediation statusRemediation status changed from Mitigation available to Awaiting fix.contact@wpscan.com ↗
- Before
- Mitigation available
- After
- Awaiting fix
- Affected versionsThe structured affected or fixed version information changed.CNA ↗
- Before
- 6.9.0 < 6.9.5; 7.0.0 < 7.0.2 · Fixed: No fixed version is explicitly recorded in the structured CVE data.
- After
- WordPress: 6.9.0 < 6.9.5, 7.0.0 < 7.0.2 · Fixed: No fixed version is explicitly recorded in the structured CVE data.
- Remediation statusRemediation status changed from Awaiting fix to Mitigation available.Canadian Centre for Cyber Security ↗
- Before
- Awaiting fix
- After
- Mitigation available
CVE published
Added to CISA KEV
Remediation guidance recorded
Technical terms and abbreviations used in this report
- CVE
- Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
- CVSS
- Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
- EPSS
- Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
- CWE
- Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
- CNA
- CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
- CISA ADP
- Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
- NVD
- National Vulnerability Database: NIST's enrichment service for CVE records.
- CERT / CSIRT
- A computer security incident response team that publishes warnings or coordinates incident response.
- PoC
- Proof of concept: public material that demonstrates or helps reproduce exploitation.
- CSAF
- Common Security Advisory Framework: a machine-readable format for security advisories.
- LoTL
- Living off the land: abuse of legitimate tools or system functions during an attack.