GP Unique ID <= 1.5.5 - Unauthenticated Form Submission Unique ID Modification
Strategic Overview
- Status
- Patched in 1.5.6
- Affected Plugin
- GP Unique ID
- Affected Version
<= 1.5.5- CVSS
- 5.3Medium
- Weakness type
- CWE-20 · Improper Input Validation
- CVE
CVE-2024-0710
At a glance
CVE-2024-0710 is a medium-severity Improper Input Validation vulnerability in the GP Unique ID WordPress plugin, affecting versions <= 1.5.5. It carries a CVSS score of 5.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 1.5.6; sites on affected versions should update now. Disclosed April 2024, reported by Karl Emil Nikka.
Vulnerability Overview
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 Analysis
The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site, and no interaction from a victim user.
CWE-20: Improper Input Validation
Reaching this weakness in GP Unique ID <= 1.5.5 takes no account at all. Improper input validation means the application accepts input without confirming it has the form, type or range the code downstream assumes.
The concrete impact depends on where the unvalidated value lands, which is why records in this class range from cosmetic bugs to full compromise. For GP Unique ID the fix is 1.5.6: builds <= 1.5.5 are affected, anything from 1.5.6 onward is not.
Remediation
Update to version 1.5.6, or a newer patched version
How does WordSec protect against this?
Requests carrying this pattern arrive without a session, so nothing upstream of the firewall gets a chance to reject them: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: GP Unique ID 1.5.6 closes this, and updating the plugin is the step that ends it.
- Firewall
- Login Security
- Alerts
External References
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C