dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2026-22490

MEDIUM · 5.4 CVSS v3.1 Published 2026-01-08
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
60/100
Remediation priority · Elevated
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Missing Authorization vulnerability in niklaslindemann Bulk Landing Page Creator for WordPress LPagery lpagery allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Bulk Landing Page Creator for WordPress LPagery: from n/a through <= 2.4.9.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

The Bulk Landing Page Creator for WordPress LPagery plugin versions up to 2.4.9 contains a missing authorization vulnerability that allows attackers to exploit incorrectly configured access control security levels. This authorization bypass likely enables lower-privileged users (or unauthenticated attackers) to access or modify landing page data they should not have permission to access.

MitigationApply any available vendor patch/ update to the plugin. Until patched, restrict plugin access to trusted administrator-level users only and monitor for suspicious activity. Consider disabling the plugin if authorization cannot be enforced.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm LPagery plugin is installed
    Navigate to WordPress admin dashboard > Plugins > Installed Plugins. Look for 'Bulk Landing Page Creator for WordPress LPagery' or 'LPagery' in the plugin list.
    Affected if The LPagery plugin appears in the installed plugins list
  2. Identify installed LPagery version
    In the Plugins page, locate the LPagery plugin entry. The version number is displayed beneath the plugin name. Compare this version to the affected range (any version up to and including 2.4.9).
    Affected if The installed version is 2.4.9 or lower
  3. Check user role access to LPagery settings
    Navigate to LPagery plugin settings (usually under Settings > LPagery or a dedicated LPagery menu item). Review which user roles (Administrator, Editor, Author, Contributor, Subscriber) have access to create, edit, or delete landing pages.
    Affected if Non-administrator roles (Editor, Author, Contributor, or Subscriber) have permission to access landing page creation or management features
  4. Verify landing page access controls
    Create a test landing page using the LPagery plugin. Then, log in as a lower-privileged user (e.g., Author or Contributor) and attempt to access the LPagery landing page list, create a new page, or modify an existing page.
    Affected if Lower-privileged users can access, create, or modify landing pages without proper authorization prompts or errors
  5. Inspect plugin capability configuration
    Check the LPagery plugin code or settings for capability requirements. In WordPress, inspect which capabilities (like 'edit_pages', 'publish_posts', or custom capabilities) are required to use the plugin's features. Compare against actual user role capabilities.
    Affected if The plugin grants landing page management capabilities to roles that should not have such access, or lacks proper capability checks

A user is affected if the LPagery plugin (version 2.4.9 or lower) is installed and allows lower-privileged users or unauthenticated users to access or modify landing page data without proper authorization checks.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply any available vendor patch/ update to the plugin. Until patched, restrict plugin access to trusted administrator-level users only and monitor for suspicious activity. Consider disabling the plugin if authorization cannot be enforced.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,290
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,664.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-22490 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-22490 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data