dbcve.org
Wp Pocket UrlsWordPress extension · Coderevolution

CVE-2024-51681

MEDIUM · 5.4 CVSS v3.1 Published 2024-11-04
Fix available
A fix is available. Upgrade to 1.0.4 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in CodeRevolution WP Pocket URLs wp-pocket-urls allows Stored XSS.This issue affects WP Pocket URLs: from n/a through <= 1.0.3.

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

Stored Cross-site Scripting (XSS) vulnerability in the WP Pocket URLs WordPress plugin allows attackers to inject malicious JavaScript code through plugin input fields, which is then stored in the database and executed when other users view affected pages.

MitigationUpdate WP Pocket URLs to the latest version when available. If no patch exists, consider using a Web Application Firewall (WAF) or disabling the plugin until a fix is released. Review user inputs and ensure proper sanitization (sanitize_text_field, esc_html, etc.) and output encoding are applied to all user-supplied data before rendering.

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
Wp Pocket UrlsWordPress extension
Affected:< 1.0.4

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
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/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 plugin is installed
    Check your WordPress plugins directory or log into the WordPress admin panel and navigate to Plugins > Installed Plugins. Look for 'WP Pocket URLs' or 'Coderevolution Wp Pocket Urls' in the list.
    Affected if The plugin is present in the WordPress installation
  2. Check installed version
    In the WordPress admin, find WP Pocket URLs in the plugin list and note the version number displayed beneath the plugin name. Alternatively, inspect the plugin header in wp-content/plugins/wp-pocket-urls/plugin.php or similar main plugin file.
    Affected if The version is less than 1.0.4
  3. Confirm input fields are accessible
    Access the plugin settings page (usually under a menu item like Pocket URLs or Settings) and identify input fields where users can submit data such as URLs, titles, or descriptions. Determine if these fields are accessible to unauthenticated users or low-privilege users.
    Affected if Input fields exist and are accessible to users who can submit data without elevated privileges
  4. Inspect database for injected scripts
    Query the WordPress database tables where plugin data is stored (look for tables with 'pocket' or 'pocket_urls' in the name, or inspect wp_postmeta for meta keys related to the plugin). Check for any stored entries containing script tags, javascript:, or other XSS payloads.
    Affected if Database contains suspicious script tags or encoded JavaScript in plugin-related tables or meta fields

The environment is affected if WP Pocket URLs plugin version is below 1.0.4 and input fields are accessible to users, indicating the stored XSS could be present or exploitable.

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.0.4 or later
Fixed in 1.0.4
Interim mitigation

Update WP Pocket URLs to the latest version when available. If no patch exists, consider using a Web Application Firewall (WAF) or disabling the plugin until a fix is released. Review user inputs and ensure proper sanitization (sanitize_text_field, esc_html, etc.) and output encoding are applied to all user-supplied data before rendering.

Recommended fix High confidence

WP Pocket URLs version 1.0.4

  1. Log in to your WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find 'WP Pocket URLs' (or 'wp-pocket-urls') in the plugin list
  4. If an update is available, click 'Update Now' to upgrade to version 1.0.4 or later
  5. Alternatively, navigate to Dashboard > Updates and apply available updates
  6. After updating, verify the plugin version is 1.0.4 or higher under Plugins > Installed Plugins

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

Fix this in Wp Pocket Urls Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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