dbcve.org
PagelayerWordPress extension

CVE-2024-30465

HIGH · 8.8 CVSS v3.1 Published 2024-06-09
Fix available
A fix is available. Upgrade to 1.8.2 or later.
See remediation →
94/100
Remediation priority · Urgent
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 Pagelayer Team PageLayer.This issue affects PageLayer: from n/a through 1.8.1.

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

Missing Authorization vulnerability in PageLayer plugin versions through 1.8.1 allows authenticated users to access privileged functionality they should not have access to, likely due to missing capability checks on AJAX actions or admin functions.

MitigationUpdate PageLayer to the latest version which includes proper authorization/capability checks for all sensitive functionality.

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

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
PagelayerWordPress extension
Affected:< 1.8.2

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
High
Integrity
High
Availability
High

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

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. Verify PageLayer plugin installation and version
    Check the plugin version in WordPress under Plugins > Installed Plugins, looking for PageLayer, or inspect the plugin header in /wp-content/plugins/pagelayer/pagelayer.php for the 'Version' comment
    Affected if The installed version is before 1.8.2
  2. Confirm WordPress user roles exist
    Navigate to Users > All Users in the WordPress admin panel and review the list of registered users
    Affected if There are any authenticated users (subscriber, contributor, author, or editor level) in the system
  3. Identify exposed AJAX actions without capability checks
    Review the plugin PHP files in /wp-content/plugins/pagelayer/ for AJAX action handlers (wp_ajax_ hooks) that lack current_user_can() or require capability checks before executing privileged operations
    Affected if AJAX actions are found that perform sensitive operations without verifying user capabilities
  4. Check admin function access controls
    Inspect admin function files in the plugin for admin menu pages or form handlers that do not include capability checks (such as manage_options or edit_posts) before allowing modifications
    Affected if Admin functions or menu pages lack proper capability verification before granting access to sensitive features

The environment is affected if PageLayer plugin version is below 1.8.2 and the site has any authenticated user accounts, since the missing capability checks would allow lower-privileged users to access privileged functionality.

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.

dbcve · scoped
Upgrade available Upgrade to 1.8.2 or later
Fixed in 1.8.2
Interim mitigation

Update PageLayer to the latest version which includes proper authorization/capability checks for all sensitive functionality.

Recommended fix Moderate confidence

1.8.2

  1. Backup your WordPress site and database before making any changes
  2. Navigate to the WordPress admin dashboard
  3. Go to Plugins > Installed Plugins
  4. Find Pagelayer in the plugin list
  5. Check if the current version is below 1.8.2
  6. If vulnerable, click 'Update now' when an update to version 1.8.2 or later is available
  7. Alternatively, you can download Pagelayer 1.8.2 from the WordPress repository and upload it manually via Plugins > Add New > Upload Plugin
  8. After updating, verify the version number reflects 1.8.2 or higher

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Pagelayer Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-30465 — 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-2024-30465 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