LiveActive security incident?Get immediate response
CVE Record

CVE-2017-20244: Wow Forms WordPress Plugin 2.1 SQL Injection

Wow Forms WordPress Plugin version 2.1 contains an SQL injection vulnerability that allows unauthenticated attackers to read arbitrary database information by exploiting an unescaped POST parameter. Attackers can inject SQL code through the 'mwpformid' parameter in requests to the admin-ajax.php endpoint with the 'send_mwp_form' action to extract sensitive database contents.

HighCVSS 8.8Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

Wow Forms 2.1 for WordPress has an unauthenticated SQL injection issue that can expose database contents. For affected sites, the main business risk is data theft from the WordPress database. The source bundle does not identify active exploitation or a confirmed vendor patch.

Executive priority

Prioritize this within the current vulnerability cycle for any public WordPress site using the plugin. If version 2.1 is present, remove or replace it quickly because database disclosure could expose users, credentials, and business content.

Technical view

The CVE describes CWE-89 SQL injection in Wow-Company Wow Forms version 2.1. An unescaped POST parameter in the plugin's AJAX form handling can allow unauthenticated attackers to read arbitrary database information. CVSS 4.0 score is 8.8 high, with high confidentiality impact and low integrity impact.

Likely exposure

Exposure appears limited to internet-facing WordPress sites running Wow Forms, also referenced as mwp-forms, specifically version 2.1. The bundle does not identify other affected versions or CPEs.

Exploitation context

The bundle cites an ExploitDB entry, so public exploit information exists. However, KEV is false and the provided sources do not show active exploitation in the wild. Treat exposed affected sites as urgent because exploitation is unauthenticated and network reachable.

Researcher notes

Evidence is sufficient for affected product, version, impact, and public exploit reference. Evidence is incomplete for patched versions, vendor remediation status, and real-world exploitation. Avoid assuming broader version ranges without confirming from vendor or code review.

Mitigation direction

  • Inventory WordPress sites for Wow Forms or mwp-forms version 2.1.
  • Disable or remove the plugin where business impact allows.
  • Check vendor and WordPress plugin guidance for a fixed or maintained version.
  • Use WAF and logging to monitor suspicious form AJAX requests.
  • Review database and WordPress accounts for unauthorized access indicators.

Validation and detection

  • Confirm whether Wow Forms or mwp-forms is installed on each WordPress site.
  • Record the installed plugin version and compare it to version 2.1.
  • Review web logs for unusual unauthenticated form submission activity.
  • Check database access logs for unexpected reads or anomalous queries.
  • Verify remediation by confirming the vulnerable plugin is removed, disabled, or updated.
Prepared
Confidence
high
Sources
5

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.

cwe · medium confidence lookup

CWE-89: Database access and collection lookup

Injection into data stores can inform collection, data access, and exfiltration detection reviews. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
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-20244 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
High
CVSS
8.8 (4.0)
Known Exploited
No
Published

Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:L/VA:N/SC:N/SI:N/SA:N

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.

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

CVSS vector scores

2 official scores

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
8.8CVSS 4.0HighCVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:L/VA:N/SC:N/SI:N/SA:NVulnCheck
8.2CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N3.94.2VulnCheck

Vulnerability scoring details

Base CVSS 4.0 score

8.8High
CVSS 4.0 vector shape for CVE-2017-20244Attack VectorAttack ComplexityAttack RequirementsPrivileges RequiredUser InteractionVS ConfidentialityVS IntegrityVS AvailabilitySS ConfidentialitySS IntegritySS Availability

Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:L/VA:N/SC:N/SI:N/SA:N

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Attack Requirements
NonePresent
Privileges Required
NoneLowHigh
User Interaction
NonePassiveActive
VS Confidentiality
HighLowNone
VS Integrity
HighLowNone
VS Availability
HighLowNone
SS Confidentiality
HighLowNone
SS Integrity
HighLowNone
SS Availability
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
Wow-CompanyWow Forms2.1Listed
Weakness

CWE details

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