LiveActive security incident?Get immediate response
CVE Record

CVE-2019-13575: A SQL injection vulnerability exists in WPEverest Everest Forms plugin for WordPress through 1.4.9.

A SQL injection vulnerability exists in WPEverest Everest Forms plugin for WordPress through 1.4.9. Successful exploitation of this vulnerability would allow a remote attacker to execute arbitrary SQL commands on the affected system via includes/evf-entry-functions.php

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

Security readout for executives and security teams

Plain-English summary

CVE-2019-13575 is a SQL injection issue in the Everest Forms WordPress plugin through 1.4.9. If a vulnerable site is reachable, a remote attacker could run unintended database queries. Business risk centers on website data exposure or manipulation, but the bundle gives no CVSS score and no confirmed active exploitation.

Executive priority

Treat this as a high-priority website hygiene issue if Everest Forms is present. The business concern is unauthorized database access on public WordPress sites. Prioritize internet-facing sites, confirm versions quickly, and remediate through vendor-supported updates rather than custom workarounds.

Technical view

The CVE states that includes/evf-entry-functions.php in WPEverest Everest Forms through 1.4.9 allowed arbitrary SQL execution by a remote attacker. Public references include the WordPress plugin developer page, a GitHub commit, WPVulnDB, and FortiGuard. The source bundle does not provide CVSS, CWE, authentication requirements, or confirmed exploit-in-the-wild evidence.

Likely exposure

Exposure is likely limited to WordPress sites running Everest Forms version 1.4.9 or earlier. Internet-facing WordPress sites are the primary concern because the CVE describes remote exploitation. Sites without this plugin, or running versions outside the affected range, are not shown as affected by the provided sources.

Exploitation context

The vulnerability is not listed in KEV in the provided bundle, and no cited source here confirms active exploitation. The stated impact is arbitrary SQL command execution, which can affect confidentiality and integrity of WordPress database content. Exact request path, privileges required, and practical exploit reliability are not established in the bundle.

Researcher notes

The bundle identifies the vulnerable file and a fixing commit reference but lacks scored severity, CWE mapping, authentication context, and exploit confirmation. Analysis should stay bounded to Everest Forms through 1.4.9 unless vendor or database records provide more detail.

Mitigation direction

  • Inventory WordPress sites for the Everest Forms plugin and installed version.
  • Update Everest Forms beyond 1.4.9 after checking vendor release guidance.
  • Back up the WordPress database before plugin remediation.
  • Review WordPress database account permissions and reduce unnecessary privileges.
  • Monitor vendor, WordPress.org, WPVulnDB, and FortiGuard guidance for clarification.

Validation and detection

  • Confirm whether Everest Forms is installed on each WordPress site.
  • Record the exact plugin version and flag 1.4.9 or earlier.
  • Review web and database logs for unusual Everest Forms-related errors or database activity.
  • Verify remediation by confirming the plugin version after update.
  • Document unaffected sites where the plugin is absent or newer than 1.4.9.
Prepared
Confidence
medium
Sources
6

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-2019-13575 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
5Source 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.