CVE-2026-9289 wordlift CVE debrief

Who should care

Defenders responsible for WordPress installations with sensitive content, especially those using the WordLift plugin, should assess exposure and prioritize remediation. This includes reviewing the current plugin version, restricting access to sensitive content, and monitoring for potential exploitation attempts. Additionally, defenders should verify and remediate this vulnerability to prevent potential exploitation and information disclosure.

Why it matters

The WordLift plugin vulnerability allows unauthenticated attackers to read sensitive metadata, bypassing WordPress access controls. Defenders should prioritize verification and remediation.

• Unauthenticated attackers can read metadata of private, draft, and pending posts
• Bypassing WordPress core access controls allows for potential information disclosure
• Defenders need to verify and remediate this vulnerability to prevent potential exploitation

Technical summary

The WordLift – AI powered SEO – Schema plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and including, 3.54.10 via the JSON-LD REST API endpoints. The vulnerability is caused by the plugin registering JSON-LD REST API endpoints with a permission_callback of '__return_true' and the downstream converter retrieving the post via get_post() without verifying the post status or the requesting user's capabilities. This allows unauthenticated attackers to read metadata of private, draft, and pending posts by enumerating post IDs, bypassing WordPress core access controls.

Defensive priority

Defenders should prioritize verifying and remediating this vulnerability, especially for WordPress installations with sensitive content.

Recommended defensive actions

• Verify the WordLift plugin version and update to a patched version if necessary
• Restrict access to sensitive content and metadata
• Monitor for potential exploitation attempts
• Review compensating controls for exposed systems while remediation is scheduled and verified
• Check relevant monitoring, detection, and logs for exposed assets that need extra review
• Track exceptions, retest remediated assets, and close the item only after evidence is documented
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up

Evidence notes

The vulnerability is caused by the plugin registering JSON-LD REST API endpoints with a permission_callback of '__return_true' and the downstream converter retrieving the post via get_post() without verifying the post status or the requesting user's capabilities.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.