WordPress security changelog
MEDIUM CVE-2025-12074 Deferred

Context Blog: A security weakness

Context Blog is affected by a security weakness. The vulnerable path is reachable without authentication. The resulting impact depends on how the affected component exposes the vulnerable operation.

CVE / CNA score 5.3 CVSS 3.1 · security@wordfence.com
NVD score Pending NVD has not published its own CVSS assessment.
Component
Context Blog
Plugin slug
context-blog
Affected
See vendor advisory
Safe version
See mitigation notes
Published
Feb 18, 2026
Weakness
CWE-200 — Exposure of Sensitive Information to an Unauthorized Actor

This CVE was published Feb 18, 2026 and is one of 2 known issues for this theme.

Update, patch or deactivate.

No fixed release is identified. Update Context Blog when a confirmed fixed release becomes available; until then, disable and remove it when the site's risk warrants.

No confirmed safe version is listed. Consider a vendor-supported patch or temporarily restricting the affected functionality while you assess the risk.

Deactivate only when warranted by your risk profile, or when advised by your hosting provider in the limited circumstances where the vulnerability cannot otherwise be mitigated. If you’re unsure which action is appropriate, contact Fused or your hosting provider for guidance.

Technical description

The Context Blog theme for WordPress is vulnerable to Information Exposure in all versions up to, and including, 1.2.5 via the 'context_blog_modal_popup' due to insufficient restrictions on which posts can be included. This makes it possible for unauthenticated attackers to extract data from password protected, private, or draft posts that they should not have access to.

CVE / CNA vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

Primary and upstream sources