Radar sectionsDatabase
Check my site
WordPress wordpress core

WordPress Core < 6.0.3 — Cross-Site Request Forgery via wp-trackback.php

ddd06190-d0c1-445d-8c6f-4c7df3248db4Published · Updated

Action summary

Affected: ≤6.0.2Update to 3.7.40 or 3.8.40 or 3.9.38 or 4.0.37 or 4.1.37 or 4.2.34 or 4.3.30 or 4.4.29 or 4.5.28 or 4.6.25 or 4.7.25 or 4.8.21 or 4.9.22 or 5.0.18 or 5.1.15 or 5.2.17 or 5.3.14 or 5.4.12 or 5.5.11 or 5.6.10 or 5.7.8 or 5.8.6 or 5.9.5 or 6.0.3 or newer

Fixed versions are per release branch: update to the fix for the branch you run.

All remediation steps
High8.8CVSS 3.18.8CISA KEVNot listedAccessNo account needed

Overview

Advisory ID
ddd06190-d0c1-445d-8c6f-4c7df3248db4
Product
WordPress wordpress
Affected
≤6.0.2
Fixed in
3.7.40, 3.8.40, 3.9.38, 4.0.37, 4.1.37, 4.2.34, 4.3.30, 4.4.29, 4.5.28, 4.6.25, 4.7.25, 4.8.21, 4.9.22, 5.0.18, 5.1.15, 5.2.17, 5.3.14, 5.4.12, 5.5.11, 5.6.10, 5.7.8, 5.8.6, 5.9.5, 6.0.3
Weakness
CWE-352 CSRF
Required access
No account needed
Published
· updated
Credit
Simon Scannell
  1. Affected≤ 6.0.2
  2. Patched in3.7.40 / 3.8.40 / 3.9.38 / 4.0.37 / 4.1.37 / 4.2.34 / 4.3.30 / 4.4.29 / 4.5.28 / 4.6.25 / 4.7.25 / 4.8.21 / 4.9.22 / 5.0.18 / 5.1.15 / 5.2.17 / 5.3.14 / 5.4.12 / 5.5.11 / 5.6.10 / 5.7.8 / 5.8.6 / 5.9.5 / 6.0.3

Update to 3.7.40 / 3.8.40 / 3.9.38 / 4.0.37 / 4.1.37 / 4.2.34 / 4.3.30 / 4.4.29 / 4.5.28 / 4.6.25 / 4.7.25 / 4.8.21 / 4.9.22 / 5.0.18 / 5.1.15 / 5.2.17 / 5.3.14 / 5.4.12 / 5.5.11 / 5.6.10 / 5.7.8 / 5.8.6 / 5.9.5 / 6.0.3 or newer.

8.8
CVSS 3.1 · CNA (Wordfence)
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
What does this vector mean?
AV:N Attack vector
Network
AC:L Attack complexity
Low
PR:N Privileges required
None
UI:R User interaction
Required
S:U Scope
Unchanged
C:H Confidentiality
High
I:H Integrity
High
A:H Availability
High

WordPress Core is vulnerable to Cross-Site Request Forgery via wp-trackback.php in versions up to 6.0.3. This is due to the fact that the any request to wp-trackback.php would assume the identity of the user whose cookies are sent with the request.

This would make it possible for an unauthenticated user to trigger a trackback assuming the identity of another user, granted they could trick that other user into performing the action. In new versions of WordPress, the identity will always be a non-existent user with the ID of 0, which represents an unauthenticated user.

Not sure which version you run? Run a passive check — it reads public files only.

Remediation & mitigations

  1. Update to one of the following versions, or a newer patched version: 3.7.40, 3.8.40, 3.9.38, 4.0.37, 4.1.37, 4.2.34, 4.3.30, 4.4.29, 4.5.28, 4.6.25, 4.7.25, 4.8.21, 4.9.22, 5.0.18, 5.1.15, 5.2.17, 5.3.14, 5.4.12, 5.5.11, 5.6.10, 5.7.8, 5.8.6, 5.9.5, 6.0.3
  2. Rotate administrator passwords and application secrets if the site ran a vulnerable version while publicly reachable.

References & provenance

Proof-of-concept & detection

No public proof-of-concept or detection template is known for this vulnerability.

Advisories & patches

Timeline

  1. CVE published

    Severity high, CVSS 8.8

  2. Record last updated

Sources & licenses

Sources & licenses

Vulnerability data
Wordfence Intelligence. Copyright 2012-2026 Defiant Inc. Licensed under the CC BY-SA 4.0.
CVSS / CWE
National Vulnerability Database (NVD), shown unmodified. This product uses the NVD API but is not endorsed or certified by the NVD.
VulnCrest content
Summary, remediation guidance and page layout © VulnCrest. Not sourced from NVD.

How we use these sources

Search VulnCrest Radar

Are you sure?