Security readout for executives and security teams
Plain-English summary
A flaw in the Kirki WordPress plugin can expose unpublished or restricted post content to anyone on the internet without authentication. Disclosed material may include drafts, private posts, password-protected posts, pending content, and trashed posts. The issue affects confidentiality; the supplied evidence does not indicate content modification or service disruption.
Executive priority
Prioritize remediation for public sites containing confidential drafts, embargoed announcements, customer information, credentials, or internal material. The technical severity is moderate, but business impact may be higher where unpublished content is sensitive. Establish exposure quickly, follow confirmed vendor remediation, and investigate access logs for possible disclosure.
Technical view
Kirki versions through 6.0.14 insufficiently validate a user-controlled key in the context parameter. An unauthenticated request using an attacker-controlled block template can reference an arbitrary post ID and retrieve its full title, content, and excerpt. This is classified as CWE-639, with CVSS 3.1 score 5.3: network-accessible, low complexity, no privileges, and confidentiality impact only.
Likely exposure
Internet-accessible WordPress sites running Kirki 6.0.14 or earlier are potentially exposed, particularly where sensitive information resides in non-public posts. The bundle does not establish whether particular configurations, themes, or endpoint restrictions reduce exposure, so organizations should validate each deployment rather than assume universal exploitability.
Exploitation context
The weakness requires no authentication or user interaction and is rated low complexity. However, the source bundle provides no evidence of active exploitation, and the CVE is not identified as being in CISA's Known Exploited Vulnerabilities catalog. Treat exploitation status as unconfirmed.
Researcher notes
The supplied evidence supports an authorization failure affecting object references rather than authentication bypass. The reported data scope is post title, content, and excerpt across multiple non-public statuses. Integrity and availability impacts are not claimed. A WordPress changeset is referenced, but the bundle does not explicitly identify the first fixed release or document configuration prerequisites.
Mitigation direction
- Inventory WordPress sites and identify Kirki installations at version 6.0.14 or earlier.
- Check official Kirki and WordPress guidance for the confirmed fixed version, then update promptly.
- If no fixed release is confirmed, disable or remove Kirki where operationally acceptable.
- Restrict public access to affected functionality as a temporary control, after testing site impact.
- Review sensitive unpublished posts and remove secrets or regulated data that need not remain stored.
Validation and detection
- Confirm the installed Kirki version on every production and staging WordPress site.
- Identify affected sites that expose the relevant Kirki frontend REST functionality to untrusted networks.
- Review web and application logs for unusual context requests referencing multiple or sensitive post identifiers.
- Conduct authorized staging validation using synthetic restricted posts, avoiding production-sensitive content.
- After remediation, verify restricted post content is unavailable to unauthenticated requests and normal pages still function.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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.
CWE-639: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCredential and access behavior lookup
The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2026-13464 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 5.3 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
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.
SSVC decision data
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N3.91.4WordfenceVulnerability scoring details
Base CVSS 3.1 score
5.3MediumVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- Source timelineWordfence
Vendor Notified
- Source timelineWordfence
Disclosed
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://www.wordfence.com/threat-intel/vulnerabilities/id/84f65255-f710-44f9-9f77-61776a40abae?source=cveCVE reference, Wordfence
- https://plugins.trac.wordpress.org/browser/kirki/tags/6.0.12/includes/API/Frontend/Controllers/CollectionController.php#L117CVE reference, Wordfence
- https://plugins.trac.wordpress.org/browser/kirki/tags/6.0.12/includes/API/Frontend/Controllers/FrontendRESTController.php#L39CVE reference, Wordfence
- https://plugins.trac.wordpress.org/browser/kirki/tags/6.0.1/includes/API/Frontend/Controllers/CollectionController.php#L117CVE reference, Wordfence
- https://plugins.trac.wordpress.org/browser/kirki/tags/6.0.1/includes/API/Frontend/Controllers/FrontendRESTController.php#L39CVE reference, Wordfence
- https://plugins.trac.wordpress.org/changeset?reponame=&old=3617070%40kirki&new=3617070%40kirkiCVE reference, Wordfence
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Authorization Bypass Through User-Controlled Key
Authorization Bypass Through User-Controlled Key represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.