LiveActive security incident?Get immediate response
CVE Record

CVE-2019-15659: The pie-register plugin before 3.1.2 for WordPress has SQL injection, a different issue than CVE-2018-10969.

The pie-register plugin before 3.1.2 for WordPress has SQL injection, a different issue than CVE-2018-10969.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

CVE-2019-15659 is a SQL injection issue in the WordPress Pie Register plugin before version 3.1.2. If an organization runs an outdated copy, attackers may be able to interfere with database-backed plugin behavior. The public sources do not provide CVSS, exploitability details, or confirmed impact scope.

Executive priority

Treat this as an inventory-driven WordPress plugin risk. It is not KEV-listed in the provided bundle, but SQL injection can affect sensitive data. Prioritize confirmed outdated, internet-facing deployments.

Technical view

The CVE record describes SQL injection in Pie Register before 3.1.2, distinct from CVE-2018-10969. The bundle does not identify the vulnerable parameter, authentication requirements, affected code path, CWE, CVSS score, or proof of active exploitation. Exposure assessment should focus on installed plugin version and reachable WordPress registration functionality.

Likely exposure

Exposure is limited to WordPress sites that installed Pie Register and have not upgraded to version 3.1.2 or later. Public-facing registration pages may increase concern, but the source bundle does not state whether authentication is required.

Exploitation context

The CVE is public and referenced by WordPress plugin and WPVulnDB pages. The bundle marks CISA KEV as false and includes no cited evidence of active exploitation, exploit maturity, or weaponized public exploit availability.

Researcher notes

Key missing details are vulnerable endpoint, parameter, authentication requirement, and exact database impact. Avoid assuming exploitability beyond the CVE description. Validate by version and exposure rather than attempting intrusive testing.

Mitigation direction

  • Upgrade Pie Register to version 3.1.2 or later.
  • Disable or remove Pie Register where it is unnecessary.
  • Check the WordPress plugin developer page for current vendor guidance.
  • Prioritize internet-facing WordPress sites with registration enabled.
  • Review database and account activity if an outdated version was exposed.

Validation and detection

  • Inventory WordPress sites for the Pie Register plugin.
  • Confirm installed Pie Register versions are 3.1.2 or later.
  • Check whether registration-related pages are publicly reachable.
  • Review web logs for unusual requests to registration functionality.
  • Verify no unexpected WordPress users or privilege changes exist.
Prepared
Confidence
medium
Sources
4

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

description · low confidence lookup

Database behavior lookup

The CVE wording references database injection or access, so collection and exfiltration review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2019-15659 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
0Timeline events
0ADP providers
3Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.