Debian Updates WordPress for XSS, Privilege Escalation, and RCE

P2 — VALIDATE AND UPDATENot provided by the authority · Not provided by the authorityEXPLOITATION: CISA KEV CONFIRMED

Quick Answer

DSA-6525-1 updates Debian 13 (trixie)'s wordpress package to 6.8.10+dfsg1-0+deb13u1 for three vulnerabilities involving cross-site scripting, privilege escalation or remote code execution. CISA lists one of them, CVE-2026-87902, as known exploited. Prioritize affected sites, but first identify their installation source: a Debian update does not necessarily replace a manually unpacked or provider-managed WordPress tree.

Confirm Scope And Apply The Supported Fix

What to do now: match the web server's active WordPress files to the Debian-managed installation. Preserve a recoverable database and corresponding site files/configuration before the package update, then validate a staging copy or controlled maintenance change. Keep plugin and theme updates separate from this core advisory.

Open the authoritative advisory

Last verified: October 2, 2026 UTC against Debian and CISA KEV catalog 2026.10.02. No site, database or plugin was tested.

Scope And Authority

Product scopeDebian 13 (trixie) wordpress packages
AdvisoryDSA-6525-1
CVEsCVE-2026-65640, CVE-2026-87902, CVE-2026-93485
Authoritative release date2026-09-28 18:41:26 UTC (Date header of Debian announcement)
Authority revision dateNo separate material revision date stated by Debian when verified
Affected versionsDebian 13 (trixie) wordpress packages before 6.8.10+dfsg1-0+deb13u1.
Fixed versionwordpress 6.8.10+dfsg1-0+deb13u1 for Debian 13 (trixie)
CVSS base scoreNot provided by the authority
CVSS severityNot provided by the authority
Exploitation statusDebian's announcement does not state exploitation. Separately, CISA KEV lists CVE-2026-87902 as known exploited, added 2026-09-25. This is CVE-level evidence, not a finding that every WordPress installation or every CVE in this notice was exploited.

What Changed

Debian corrected three WordPress vulnerabilities that could result in cross-site scripting, privilege escalation, or remote code execution and recommends upgrading the affected package.

What To Validate Now

  1. Identify the served code. Record the actual document root, deployment owner and installed Debian package. A fixed package elsewhere on the host does not establish the version serving requests.
  2. Prepare recovery. Preserve a consistent database backup, uploads, configuration and required site files, with a known restore procedure. Do not assume copying only the application directory captures the site.
  3. Apply the matching update. For the Debian-managed installation, use the trixie security package. For an independently managed copy, follow that deployment's supported update path instead of treating this Debian version string as its upstream target.
  4. Validate the site. Test public rendering, authorized login, draft editing/publishing and required plugin/theme behavior. Confirm a low-privilege account still cannot perform administrative actions; use approved test content without exposing secrets.
  5. Retain deployment evidence. Keep the package/deployment identity, recovery point and test outcomes. Investigate compromise indicators separately; an update does not remove all possible attacker persistence.

Operational Cautions

Coordinate application, database and cache behavior during maintenance. Do not overwrite local configuration or custom content to resolve a package conflict without understanding its ownership. CISA's October 2 KEV catalog records CVE-2026-87902 as added September 25 and flags forensic triage. Preserve relevant site and access evidence before destructive cleanup, and escalate suspicious findings through incident response. Known exploitation of this CVE does not show that every listed CVE was exploited or that this site was compromised. Core remediation does not establish the security of plugins or themes.

Evidence To Retain

  • Exact product, release stream, package or application version, enabled feature, environment, and accountable owner.
  • UTC timestamps, authority revision, approved change record, installer or package-manager output, and resulting version.
  • Relevant logs and monitoring evidence, test results, exceptions, compensating controls, and rollback decisions.

Related TechGeeks Resources

Authoritative References

Correction policy: If the authority changes affected versions, fixed versions, severity, exploitation information, mitigations, or required action, TechGeeks will update this notice and its verification date.