CVE-2026-110019 niklaslindemann CVE debrief

Who should care

WordPress administrators and defenders responsible for securing WordPress installations should assess exposure to this vulnerability and prioritize verification and remediation efforts.

Why it matters

CVE-2026-110019 is a medium-severity vulnerability in the Bulk Page Generator – LPagery plugin for WordPress, allowing authorization bypass and potential creation, modification, and deletion of LPagery-managed pages and processes by authenticated attackers with subscriber-level access.

• Authenticated attackers with subscriber-level access can create, modify, and delete LPagery-managed WordPress pages and bulk page-generation processes.
• Defenders must verify the presence of this vulnerability in their WordPress installations and restrict access to the plugin's functionality.
• The exact scope of affected versions and deployments requires further verification from official sources.

Technical summary

The Bulk Page Generator – LPagery plugin for WordPress is vulnerable to authorization bypass due to improper verification of user authorization. This allows authenticated attackers with subscriber-level access and above to create, modify, and delete LPagery-managed WordPress pages and bulk page-generation processes. On default fresh installations where Freemius has not been opted into, the AES-256-CBC key used to validate Bearer tokens collapses to the publicly known SHA-256 hash of an empty string, making the token entirely forgeable by any authenticated user. Defenders should prioritize verifying the presence of this vulnerability in their WordPress installations and restrict access to the plugin's and bulk

Defensive priority

Defenders should prioritize verifying the presence of this vulnerability in their WordPress installations and restrict access to the plugin's functionality.

Recommended defensive actions

• Verify the presence of the Bulk Page Generator – LPagery plugin in your WordPress installation.
• Restrict access to the plugin's functionality to authorized users only.
• Consider upgrading to a version of the plugin that addresses this vulnerability, if available.
• 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 CVE record and NVD entry provide details on the vulnerability, including its description and CVSS score. However, the exact scope of affected versions and deployments requires further verification.

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.