Skip to main content
CVE-2026-115282VulnerabilityPublished

The Recipe Card Blocks Lite WordPress plugin before 3.6.4 does not perform an authorization check before rendering

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-115282· Medium

Not known to be exploited : upgrade to 3.6.4 when convenient.

Data as of 29 Oct 2026, 07:10 UTC

Severity
Medium

Rated Medium by Threat Radar's AI analysis · CVSS not yet scored by NVD

Thin evidence

One scorer or none
Patch
Available – fixed in 3.6.4

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 29 Oct 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.

What to do

Upgrade Recipe Card Blocks Lite (WordPress plugin) to 3.6.4.

Affected software

ProductAffectedFixed in
Recipe Card Blocks LiteAffected
  • >=2.6.4 <3.6.4
Fixed in
  • 3.6.4

AI-suggested

Upgrade the Recipe Card Blocks Lite WordPress plugin to version 3.6.4 or later, where this authorization check issue is fixed. No other mitigation is effective because the optional 'print only published posts' protection does not prevent the vulnerability.

Description

The Recipe Card Blocks Lite WordPress plugin versions before 3.6.4 have a vulnerability where unauthenticated users can access unpublished post details through the recipe print feature. This flaw allows disclosure of titles, IDs, and recipe content from drafts, pending, private, and password-protected posts containing recipe card blocks. The plugin's optional protection to print only published posts is ineffective because it checks the status of a different post than the one rendered.

References

Community reviews

Loading reviews…