Missing AuthorizationWeakness · CWE-862

CVE-2024-49686

MEDIUM · 5.4 CVSS v3.1 Published 2024-12-31
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 fatcatapps Landing Page Cat landing-page-cat.This issue affects Landing Page Cat: from n/a through <= 1.7.4.

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 the fatcatapps Landing Page Cat WordPress plugin allows authenticated users (with subscriber-level access or higher) to perform actions that should require higher privileges. The plugin fails to properly verify user capabilities before executing certain functions, potentially allowing unauthorized access to administrative features or data.

MitigationUpdate to the latest version of Landing Page Cat which includes proper authorization checks. If no update is available, manually add current_user_can() capability checks and nonce verification to all functions that perform privileged operations.

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. Locate the Landing Page Cat plugin installation
    Check the wp-content/plugins/ directory for a folder named 'landing-page-cat', 'landing-page-cat-wordpress', or similar fatcatapps plugin directories. Also check the WordPress admin plugin list.
    Affected if The plugin folder exists in the plugins directory, indicating the plugin is installed
  2. Identify the installed plugin version
    Open the main plugin PHP file (usually plugin-name.php in the plugin folder) and locate the 'Version' header in the plugin comment block at the top of the file.
    Affected if The version displayed does not match the latest patched version, or cannot be determined to include the authorization fix
  3. Check user role configuration
    In WordPress admin, go to Users > Users List and verify if any users have the 'Subscriber' role assigned. Also check if any low-privileged custom roles exist that may have been granted access.
    Affected if There are users with Subscriber-level access or any custom role that should not have administrative capabilities
  4. Verify capability enforcement on plugin actions
    As a test, attempt to access plugin functions or admin pages that should require administrator privileges while logged in as a subscriber-level user. Check if the plugin properly blocks unauthorized actions.
    Affected if The plugin allows subscriber-level users to access or execute functions that should be restricted to administrators
  5. Inspect plugin code for capability checks
    Examine the main plugin PHP files for the presence of current_user_can() calls before sensitive operations, and verify that nonce verification exists for form submissions and AJAX actions.
    Affected if The plugin code lacks proper current_user_can() checks or nonce verification before performing privileged operations

A user is affected if the Landing Page Cat plugin is installed, the installed version predates the patched version with authorization fixes, and subscriber-level or lower-privileged users can access administrative features.

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

Update to the latest version of Landing Page Cat which includes proper authorization checks. If no update is available, manually add current_user_can() capability checks and nonce verification to all functions that perform privileged operations.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,780
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

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-49686 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