dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2024-4997

MEDIUM · 5.3 CVSS v3.1 Published 2024-06-04
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges 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
The WPUpper Share Buttons plugin for WordPress is vulnerable to unauthorized access of data when preparing sharing links for posts and pages in all versions up to, and including, 3.43. This makes it possible for unauthenticated attackers to obtain the contents of password protected posts and pages.

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 · high confidence

The WPUpper Share Buttons plugin for WordPress (versions up to 3.43) contains a broken access control vulnerability in its sharing link generation functionality. Unauthenticated attackers can exploit this to bypass WordPress password protection and retrieve the contents of password-protected posts and pages through specially crafted requests to the plugin's share link preparation logic.

MitigationUpdate the WPUpper Share Buttons plugin to version 3.44 or later to patch the unauthorized access vulnerability. Until patched, consider disabling the plugin or deploying a WAF rule to block attempts to access password-protected content via the share functionality.

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
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
None

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

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 WPUpper Share Buttons plugin is installed
    Log in to WordPress admin dashboard, go to Plugins > Installed Plugins, and look for 'WPUpper Share Buttons' in the list. Note the version number displayed beneath the plugin name.
    Affected if The plugin is present and the version is 3.43 or lower
  2. Check the plugin version directly via filesystem
    If you have filesystem access, navigate to /wp-content/plugins/wpupper-share-buttons/ and open the main plugin PHP file (usually named wpupper-share-buttons.php or similar) to read the version defined in the plugin header comment.
    Affected if The version returned is 3.43 or lower (any version up to and including 3.43 is vulnerable)
  3. Identify password-protected content
    In WordPress admin, go to Posts > All Posts and filter or search for posts with a padlock icon indicating password protection. Alternatively, query the WordPress database: SELECT ID, post_title FROM wp_posts WHERE post_password != '' AND post_status = 'publish';
    Affected if There are password-protected posts or pages on the site that could be accessed via the vulnerability
  4. Test share link endpoint accessibility
    Submit a request to the plugin's share link preparation endpoint. The vulnerable endpoint is typically reachable via POST or GET to the site root with parameters related to share button generation (the exact parameter names vary but involve share link generation logic). Check if unauthenticated requests can trigger share link generation for protected content.
    Affected if The share link generation functionality processes requests without requiring authentication or validating password protection status

If WPUpper Share Buttons version 3.43 or lower is installed and your site has password-protected content, you are affected by this vulnerability.

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

Update the WPUpper Share Buttons plugin to version 3.44 or later to patch the unauthorized access vulnerability. Until patched, consider disabling the plugin or deploying a WAF rule to block attempts to access password-protected content via the share functionality.

Recommended fix High confidence

WPUpper Share Buttons version 3.44 or later

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate 'WPUpper Share Buttons' in the plugin list
  4. If an update is available, click 'Update Now' to update to version 3.44 or later
  5. Alternatively, navigate to Dashboard > Updates to update all plugins
  6. After updating, verify that password-protected posts/pages are no longer accessible to unauthenticated users through the sharing links

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing3.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,210
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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