dbcve.org
Information ExposureWeakness · CWE-200

CVE-2025-12074

MEDIUM · 5.3 CVSS v3.1 Published 2026-02-18
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The Context Blog WordPress theme has an information disclosure vulnerability in the 'context_blog_modal_popup' function. This function lacks proper authorization checks, allowing unauthenticated attackers to query and retrieve content from password-protected, private, or draft posts that should be restricted. The vulnerability stems from insufficient validation of which posts the modal popup can access.

MitigationUpdate the Context Blog theme to version 1.2.6 or later which contains the access control fix. If unable to update immediately, restrict access to the affected function or implement custom authorization checks in the theme.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
None

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm Context Blog theme is installed
    Inspect the wp-content/themes/context-blog directory, or check WordPress admin under Appearance > Themes
    Affected if The Context Blog theme is present in the themes directory or active in WordPress
  2. Determine the installed theme version
    Open the theme's style.css file in wp-content/themes/context-blog/ and locate the 'Version:' header in the CSS comment block, or view theme details in WordPress admin
    Affected if The version field shows a number lower than 1.2.6 (e.g., 1.2.5, 1.2.4, 1.0.0)
  3. Locate the vulnerable modal popup function
    Search theme files (particularly functions.php or includes/*.php) for the string 'context_blog_modal_popup'
    Affected if The function 'context_blog_modal_popup' exists in the theme code
  4. Verify authorization is missing in the function
    Examine the context_blog_modal_popup function code and look for WordPress capability checks like 'current_user_can', 'is_user_logged_in', or post visibility checks (private_posts, password_protected, draft)
    Affected if The function contains no authorization checks and directly queries post content without validating user permissions or post visibility
  5. Confirm modal popup feature is enabled
    Check theme customizer settings (Appearance > Customize > Theme Options) or theme settings in WordPress admin for any modal/popup-related configuration, or inspect page templates that invoke the modal popup
    Affected if The modal popup feature is actively used on the site and the theme version is below 1.2.6

A user is affected if the Context Blog theme is installed with a version lower than 1.2.6 and the context_blog_modal_popup function exists without proper authorization checks.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the Context Blog theme to version 1.2.6 or later which contains the access control fix. If unable to update immediately, restrict access to the affected function or implement custom authorization checks in the theme.

Recommended fix Moderate confidence

Theme version 1.2.6 or latest available version

  1. Locate the Context Blog theme in your WordPress installation at wp-content/themes/context-blog
  2. Check the current theme version in style.css or theme details
  3. Update the theme to the latest available version from wordpress.org/theme repository or the theme developer (postmagthemes.com)
  4. After updating, verify that password protected, private, and draft posts are no longer accessible via the context_blog_modal_popup functionality
Caveat Theme updates may include template changes; backup customizations before updating

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-12074 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-12074 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data