dbcve.org
Pie RegisterWordPress extension · Genetechsolutions

CVE-2019-15659

CRITICAL · 9.8 CVSS v3.0 Published 2019-08-27
Fix available
A fix is available. Upgrade to 3.1.2 or later.
See remediation →
100/100
Remediation priority · Urgent
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 pie-register plugin before 3.1.2 for WordPress has SQL injection, a different issue than CVE-2018-10969.

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 pie-register WordPress plugin before version 3.1.2 contains a SQL injection vulnerability that allows attackers to inject malicious SQL queries through unsanitized input parameters, potentially enabling unauthorized data access, modification, or deletion of the database.

MitigationUpgrade the pie-register plugin to version 3.1.2 or later to apply the security patch. If immediate patching is not possible, consider temporarily disabling the plugin until the update can be applied.

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
Pie RegisterWordPress extension
Affected:< 3.1.2

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
High
Integrity
High
Availability
High

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

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. Locate the pie-register plugin files
    Check the WordPress plugins directory (wp-content/plugins/) for a folder named 'pie-register' or similar naming convention used by Genetechsolutions.
    Affected if The plugin folder is present in the plugins directory.
  2. Identify the installed plugin version
    Open the main plugin file (typically pie-register.php or index.php inside the plugin folder) and locate the version declaration in the plugin header comment.
    Affected if The version number found is less than 3.1.2, or no version header is present and the plugin appears to be an older release.
  3. Confirm the plugin is active
    Query the WordPress options table (wp_options) for the 'active_plugins' option, or check through the WordPress admin plugins list to see if pie-register is currently enabled.
    Affected if The pie-register plugin is listed as active in the site's plugin configuration.
  4. Verify user registration functionality is in use
    Check if any registration forms created with pie-register are published and accessible on the site, or review the plugin settings for enabled registration workflows.
    Affected if Registration forms or endpoints handled by pie-register are publicly accessible and processing user input.

A user is affected if the pie-register plugin is installed, active, running version 3.1.1 or lower, and handling user input through its registration forms.

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 3.1.2 or later
Fixed in 3.1.2
Interim mitigation

Upgrade the pie-register plugin to version 3.1.2 or later to apply the security patch. If immediate patching is not possible, consider temporarily disabling the plugin until the update can be applied.

Recommended fix High confidence

Pie Register 3.1.2 or later

  1. 1. Back up your WordPress database and files before making any changes
  2. 2. Navigate to WordPress admin dashboard > Plugins > Installed Plugins
  3. 3. Locate Pie Register in the plugin list
  4. 4. Click 'Update now' if an update is available, or manually upload Pie Register version 3.1.2 or later
  5. 5. After updating, clear any caching plugins if present
  6. 6. Verify the plugin is running version 3.1.2 or later under Plugins > Installed Plugins
Caveat Minor plugin version updates typically do not introduce breaking changes; test in a staging environment first if possible

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

Fix this in Pie Register Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing3.0 h
  • Review / QA2.0 h
8.0 hours of engineering $1,390
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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