LiveActive security incident?Get immediate response
CVE Record

CVE-2026-22490: WordPress Bulk Landing Page Creator for WordPress LPagery plugin <= 2.4.9 - Broken Access Control vulnerability

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.

MediumCVSS 5.4Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2026-22490 affects the WordPress LPagery plugin, used to create bulk landing pages. A logged-in user may perform actions they should not be authorized to perform. The published severity is medium, with limited integrity and availability impact. There is no source evidence of active exploitation or CISA KEV listing.

Executive priority

Treat as a routine but timely WordPress plugin remediation item. Prioritize sites where many non-admin users can log in, because exploitation requires authentication. No public source provided confirms active exploitation, but broken access control can affect site integrity and operations.

Technical view

The issue is a Missing Authorization vulnerability (CWE-862) in niklaslindemann Bulk Landing Page Creator for WordPress LPagery through version 2.4.9. CVSS 3.1 is 5.4: network exploitable, low complexity, low privileges required, no user interaction, unchanged scope, with low integrity and availability impact and no confidentiality impact.

Likely exposure

Exposure is limited to WordPress sites with the LPagery plugin installed at an affected version. The CVSS vector indicates an authenticated low-privilege attacker is required, reducing broad internet-wide risk compared with unauthenticated flaws.

Exploitation context

Sources do not report active exploitation, public weaponization, or KEV inclusion. The risk is most relevant where untrusted or numerous users can authenticate to WordPress, such as contributor, customer, membership, or agency-managed sites.

Researcher notes

The source bundle contains a version inconsistency: the title states affected through 2.4.9, while the Patchstack URL text references 2.4.4. The CVE description states through 2.4.9. No patch version or detailed affected endpoint is provided in the supplied sources.

Mitigation direction

  • Identify WordPress sites using the LPagery plugin.
  • Check whether installed LPagery versions are 2.4.9 or earlier.
  • Review the vendor and Patchstack pages for fixed-version guidance.
  • Limit WordPress accounts to necessary users and roles.
  • Remove or disable the plugin where it is not required.

Validation and detection

  • Inventory WordPress plugins across production, staging, and managed customer sites.
  • Confirm LPagery version from the WordPress admin interface or asset inventory.
  • Review WordPress user roles for unnecessary low-privilege accounts.
  • Check site logs for unexpected LPagery-related administrative actions.
  • Track CVE, vendor, and Patchstack updates for remediation details.
Prepared
Confidence
medium
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-862: Authorization and privilege behavior lookup

Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-22490 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
5.4 (3.1)
Known Exploited
No
Published

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

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
5.4CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L2.82.5Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

5.4Medium
CVSS 3.1 vector shape for CVE-2026-22490Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
niklaslindemannBulk Landing Page Creator for WordPress LPagerylpagery, 0unaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-862 · source CWE mapping

Missing Authorization

Missing Authorization represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.