Security readout for executives and security teams
Plain-English summary
A WordPress contact-form add-on had an unauthenticated SQL injection issue in versions up to 3.1.23. An attacker could potentially read sensitive database data and cause limited availability impact. The bundle does not cite active exploitation or name a fixed version.
Executive priority
Prioritize this as high for any public WordPress property using the affected plugin. The main concern is confidential data exposure from the database. Absence from KEV lowers evidence of known exploitation, but it does not reduce the need to identify and remediate vulnerable installations.
Technical view
CVE-2022-47586 is CWE-89 SQL injection in Themefic Ultimate Addons for Contact Form 7, package ultimate-addons-for-contact-form-7, affecting versions <= 3.1.23. CVSS 3.1 is 8.2: network-accessible, low complexity, no privileges, user interaction required, changed scope, high confidentiality impact, no integrity impact, low availability impact.
Likely exposure
Exposure is likely limited to WordPress sites running Themefic Ultimate Addons for Contact Form 7 at version 3.1.23 or earlier. Internet-facing WordPress sites have higher business relevance because the vulnerability is network reachable and does not require authentication.
Exploitation context
The source bundle says unauthenticated SQL injection, but CVSS marks user interaction as required. KEV is false, and the provided sources do not state active exploitation or provide exploit availability. Treat exploit status as unconfirmed from this evidence.
Researcher notes
Evidence is sparse: the bundle identifies the vulnerability class, product, package, affected threshold, CVSS, and Patchstack entry, but not the vulnerable parameter, proof of exploitation, or fixed version. Avoid exploit testing unless authorized and scoped; use version and configuration validation first.
Mitigation direction
- Inventory WordPress sites for the Ultimate Addons for Contact Form 7 plugin.
- Disable or remove vulnerable versions if the plugin is not business-critical.
- Check Themefic and Patchstack guidance for a vendor-confirmed fixed release.
- Upgrade only to a release confirmed by the vendor or Patchstack as fixed.
- Limit database account privileges used by WordPress where operationally feasible.
- Monitor WordPress and database logs for suspicious contact-form-related activity.
Validation and detection
- Confirm whether the plugin is installed on each WordPress site.
- Record the installed plugin version and compare it with <= 3.1.23.
- Verify whether the plugin is active or reachable on public pages.
- Check vendor or Patchstack advisories for the current fixed-version guidance.
- Review recent web and database logs for unusual requests or errors.
- Document exceptions where removal or upgrade is delayed.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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-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 lookupDatabase 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 lookupCVE-2022-47586 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 8.2 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:N/A:L
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.
CVSS vector scores
1 official scoreWe 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.
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:N/A:L2.84.7Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
8.2HighVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:N/A:L
Source materials
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.