dbcve.org
Improper Input ValidationWeakness · CWE-20

CVE-2024-0710

MEDIUM · 5.3 CVSS v3.1 Published 2024-05-02
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 GP Unique ID plugin for WordPress is vulnerable to Unique ID Modification in all versions up to, and including, 1.5.5. This is due to insufficient input validation. This makes it possible for unauthenticated attackers to tamper with the generation of a unique ID on a form submission and replace the generated unique ID with a user-controlled one, leading to a loss of integrity in cases where the ID's uniqueness is relied upon in a security-specific context.

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 GP Unique ID WordPress plugin fails to properly validate or sanitize input during unique ID generation, allowing unauthenticated attackers to manipulate the ID value submitted with form data and replace the server-generated unique ID with an attacker-controlled value, compromising integrity where uniqueness is used for security purposes.

MitigationUpdate to version 1.5.6 or later which includes proper input validation. If immediate update is not possible, implement server-side validation of unique ID submissions and monitor for anomalous ID values in form submissions.

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
None
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/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 GP Unique ID plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'GP Unique ID' or 'Unique ID' in the list. Alternatively, check the /wp-content/plugins/ directory for a folder containing 'gp-unique-id' or similar.
    Affected if The plugin is present in the WordPress installation
  2. Determine installed plugin version
    In WordPress admin, click on the GP Unique ID plugin to view details and note the version number. Alternatively, check the main plugin PHP file header for the 'Version' field.
    Affected if Version is lower than 1.5.6 (vulnerable)
  3. Identify active forms using unique ID
    Check WordPress form plugins (Gravity Forms, WPForms, etc.) for fields or feeds that utilize the GP Unique ID add-on. Look for 'unique ID' field assignments in form settings.
    Affected if Forms are configured to generate unique IDs that could be overwritten
  4. Inspect recent form submissions for anomalous ID values
    Export or query form submission logs. Look for ID values that follow predictable patterns vs. seemingly random/complex values that may indicate attacker manipulation.
    Affected if Form entries contain ID values that don't match expected server-generated format or show suspicious patterns
  5. Check server logs for unique ID manipulation attempts
    Review web server access logs for POST requests to form endpoints containing unusual or long ID parameter values. Search for the unique ID field name in HTTP requests.
    Affected if Logs show ID field values that appear user-controlled rather than server-generated

If GP Unique ID plugin version is below 1.5.6 and forms are using the unique ID feature, the environment is likely affected by this integrity bypass 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 to version 1.5.6 or later which includes proper input validation. If immediate update is not possible, implement server-side validation of unique ID submissions and monitor for anomalous ID values in form submissions.

Recommended fix Moderate confidence

Update to GP Unique ID version 1.5.6 or later (the latest available version)

  1. 1. Back up your WordPress site and database before making any changes.
  2. 2. Navigate to Plugins > Installed Plugins in your WordPress admin dashboard.
  3. 3. Locate the GP Unique ID plugin in the list.
  4. 4. Check if an update is available for the plugin.
  5. 5. If an update is available, click 'Update Now' to install the latest version.
  6. 6. After updating, verify the plugin is working correctly by testing form submissions that use the unique ID field.
  7. 7. Confirm the unique IDs are being generated correctly and not accepting user-supplied values.

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
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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