{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-110019 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-110019 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-110019 is a medium-severity missing authorization vulnerability in niklaslindemann Bulk Page Generator – LPagery, published on 16 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-110019 and fix it if it is affected.\n\nWhat it is: CVE-2026-110019 is a medium-severity missing authorization vulnerability in niklaslindemann Bulk Page Generator – LPagery, published on 16 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-110019 in the wild and no public exploit code.\n\nAffected product: niklaslindemann Bulk Page Generator – LPagery. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-110019/ (Markdown: https://insights.sbomify.com/CVE-2026-110019/index.md)","id":"CVE-2026-110019","markdown":"https://insights.sbomify.com/CVE-2026-110019/index.md","name":"CVE-2026-110019","record":{"aliases":["GHSA-3469-85w2-9x78"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["data_modify","privilege_escalation"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress plugin","requires_auth":"low_privilege","summary":"Authenticated subscribers can create, modify, or delete restricted pages due to missing authorization checks and forgeable tokens.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Wordfence","cpe":[],"cvss":{"score":4.3,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-862","name":"Missing Authorization"}],"description":"The Bulk Page Generator – LPagery plugin for WordPress is vulnerable to authorization bypass in all versions up to, and including, 3.1.0 This is due to the plugin not properly verifying that a user is authorized to perform an action. This makes it possible for authenticated attackers, with subscriber-level access and above, to create, modify, and delete LPagery-managed WordPress pages and bulk page-generation processes that are otherwise restricted to administrators. 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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Missing authorization in Bulk Page Generator – LPagery","id":"CVE-2026-110019","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"missing_authorization","year":"2026"},"n_packages":0,"n_references":6,"next":{"headline":"The Rich Showcase for Google Reviews plugin for WordPress is vulnerable to authorization bypass in all versions up to, and including, 7.1.6","id":"CVE-2026-110020"},"packages":[],"prev":{"headline":"aBlocks \u003c= 2.17.0 - Authenticated (Contributor+) Privilege Escalation to 'roleSlug' Block Attribute","id":"CVE-2026-110018"},"products":["Bulk Page Generator – LPagery"],"published":"2026-10-16","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-10-16","vendors":["niklaslindemann"]},"summary":"Authenticated subscribers can create, modify, or delete restricted pages due to missing authorization checks and forgeable tokens.","url":"https://insights.sbomify.com/CVE-2026-110019/"}