dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2024-32797

MEDIUM · 5.4 CVSS v3.1 Published 2024-06-09
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 Martin Gibson WP LinkedIn Auto Publish.This issue affects WP LinkedIn Auto Publish: from n/a through 8.11.

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 WP LinkedIn Auto Publish WordPress plugin allows unauthenticated or low-privilege users to potentially access administrative functions or perform actions without proper capability verification. The plugin fails to validate user permissions before executing sensitive operations related to LinkedIn content publishing.

MitigationAdd proper capability checks and nonce verification to all AJAX handlers and admin pages in the plugin. Ensure only users with appropriate permissions (e.g., manage_options or specific custom capability) can trigger LinkedIn publishing actions.

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. Verify the plugin is installed and active
    Go to WordPress Admin > Plugins and look for 'WP LinkedIn Auto Publish' in the installed plugins list. Check if it shows as 'Active'.
    Affected if The plugin is installed and active, exposing the vulnerable code.
  2. Identify the installed plugin version
    Click on the plugin name in the Plugins list to view its details, or open the main plugin file (wp-linkedin-auto-publish.php) and locate the version constant/comment in the file header.
    Affected if Running any version of the plugin without the authorization fix (version comparison to the patched release is required).
  3. Check if LinkedIn publishing is configured
    Navigate to the plugin settings page (usually under Settings or a dedicated LinkedIn menu item). Look for fields to enter LinkedIn API credentials (Client ID, Client Secret) and a connection status indicator.
    Affected if The plugin has valid LinkedIn API credentials configured, enabling the publishing functionality that lacks authorization checks.
  4. Inspect AJAX endpoints for capability checks
    Examine the plugin PHP files for AJAX handlers (wp_ajax_ and wp_ajax_nopriv_ hooks). Search for functions that handle publishing actions. Look for current_user_can() or capability verification calls in these handlers.
    Affected if AJAX endpoints related to LinkedIn publishing lack proper current_user_can() capability checks, especially those accessible to unauthenticated users (wp_ajax_nopriv_).
  5. Check admin page access controls
    Review the plugin admin menu registration and page rendering code. Look for admin_init or admin_menu hooks that render the plugin settings. Verify if these pages include admin access validation.
    Affected if The plugin admin pages or settings actions can be accessed by any logged-in user without verifying they have administrator-level permissions.

A user is affected if the plugin is active with LinkedIn credentials configured and the code lacks proper current_user_can() checks on AJAX handlers or admin pages handling publishing actions.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Add proper capability checks and nonce verification to all AJAX handlers and admin pages in the plugin. Ensure only users with appropriate permissions (e.g., manage_options or specific custom capability) can trigger LinkedIn publishing actions.

Recommended fix Moderate confidence

WP LinkedIn Auto Publish version 8.12 or later

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate WP LinkedIn Auto Publish
  4. Check if an update is available and update to version 8.12 or later
  5. Alternatively, download the latest version from the WordPress plugin repository or the vendor's website and upload via Plugins > Add New > Upload Plugin
  6. Activate the updated plugin

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

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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