---
id: "CVE-2026-115282"
kind: "vulnerability"
aliases: ["CVE-2026-115282"]
title: "WordPress Recipe Card Blocks Lite: unauthenticated users read unpublished post content"
severity: "medium"
cvss: null
epss: null
exploited: false
status: "open"
category: "package"
products: []
ecosystems: []
tags: ["package", "recipe-card-blocks-lite", "wordpress"]
not_affected_if: ["plugin-not-installed", "plugin-updated-3.6.4"]
published_at: "2026-10-29T06:17:19+00:00"
first_seen_at: "2026-10-29T06:53:13+00:00"
updated_at: "2026-10-29T06:54:43+00:00"
sources: [{"source": "nvd", "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-115282", "first_seen_at": "2026-10-29T06:53:13+00:00"}]
---

# WordPress Recipe Card Blocks Lite: unauthenticated users read unpublished post content

The Recipe Card Blocks Lite WordPress plugin before 3.6.4 renders posts through its recipe print feature without an authorization check. An unauthenticated visitor can read the title, ID and recipe content of drafts, pending, private and password-protected posts that contain a recipe card block.

_Summary, check and fix written by a model from the sources; labelled as such._

## How to check

- Check the installed version of Recipe Card Blocks Lite in the WordPress admin plugin list; it is affected below `3.6.4`.
- Look for the plugin's recipe print URLs on the site and test whether unpublished posts with a recipe card render without logging in.

## Fix

- Recipe Card Blocks Lite: `3.6.4` or later (per the NVD description, the fix is in versions from 3.6.4).

## Timeline

- 2026-10-29T06:53:13+00:00 nvd https://nvd.nist.gov/vuln/detail/CVE-2026-115282

## From the sources

The Recipe Card Blocks Lite WordPress plugin before 3.6.4 does not perform an authorization check before rendering posts through its recipe print feature, allowing unauthenticated users to disclose the title, ID and recipe content of unpublished posts, including drafts, pending, private and password-protected posts, that contain a recipe card block. Its optional "print only published posts" protection does not prevent this, because the status check is applied to a different post than the one ultimately rendered.

---

_Free to read at a human pace. An API with keys and an MCP server are in preparation; early access: hello@infrastack.ai_