LiveActive security incident?Get immediate response
CVE Record

CVE-2017-14723: Before version 4.8.2, WordPress mishandled % characters and additional placeholder values in $wpdb->prepare...

Before version 4.8.2, WordPress mishandled % characters and additional placeholder values in $wpdb->prepare, and thus did not properly address the possibility of plugins and themes enabling SQL injection attacks.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2017-14723 is a WordPress core flaw fixed in 4.8.2. WordPress incorrectly handled percent characters and extra placeholders in database query preparation, which could let vulnerable plugins or themes create SQL injection risk. The record does not show active exploitation via KEV.

Executive priority

Prioritize remediation if any internet-facing WordPress site still runs pre-4.8.2 core. For maintained sites already on modern WordPress, this is mainly a legacy exposure and due-diligence item tied to plugin, theme, and asset inventory hygiene.

Technical view

Before WordPress 4.8.2, $wpdb->prepare mishandled % characters and additional placeholder values. The issue was in core query-preparation behavior, but exploitation depends on plugin or theme code paths that expose attacker-controlled input into affected prepared-query patterns.

Likely exposure

Exposure is most likely on WordPress installations older than 4.8.2, especially sites with custom or third-party plugins and themes using $wpdb->prepare. Debian-packaged WordPress users should check DSA-3997 coverage. Current supported WordPress versions should not be exposed to this historical core flaw.

Exploitation context

The source bundle includes public technical write-ups and a PoC reference, but KEV is false and no cited source here confirms active exploitation. Treat it as a known public vulnerability that can become relevant when old WordPress core and vulnerable plugin or theme code coexist.

Researcher notes

The CVE description is narrow: core mishandling in $wpdb->prepare could enable SQL injection through plugins and themes. The bundle lacks CVSS, CWE, precise affected CPEs, and confirmed exploit-in-the-wild evidence, so validation should focus on version state and reachable dependent code paths.

Mitigation direction

  • Upgrade WordPress core to 4.8.2 or a current supported release.
  • Apply Debian DSA-3997 updates where WordPress is installed from Debian packages.
  • Update all plugins and themes to maintained versions.
  • Audit custom code using $wpdb->prepare for affected placeholder patterns.
  • Check official WordPress and package-vendor guidance before relying on compensating controls.

Validation and detection

  • Inventory WordPress core versions and flag anything older than 4.8.2.
  • Confirm package-manager status against Debian DSA-3997 where applicable.
  • Review custom plugins and themes for $wpdb->prepare usage with user input.
  • Verify production and staging run the same patched core lineage.
  • Check web and database logs for suspicious SQL error patterns.
Prepared
Confidence
medium
Sources
10

Public sources used

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-2017-14723 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
9Source 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.