HexBrain

Browse / CVEs / CVE-2023-33405

CVE-2023-33405· blogengine / blogengine.net· CWE-601

BlogEngine CMS - Open Redirect

mediumseverity
6.1CVSS score
31.3%likelihood of exploitation, next 30 days
98%of all CVEs are less likely
Readycheck to confirm it

Blogengine.net 3.3.8.0 and earlier is vulnerable to Open Redirect

Impact

Unauthenticated attackers can exploit open redirect through the years parameter to redirect users to malicious websites for phishing attacks.

Fix

Update to the latest version of blogengine.net CMS to fix the open redirect vulnerability.

How to confirm it

Send: GET {{BaseURL}}/default.aspx?years=http://oast.pro
Positive when: matches in header /(?m)^(?:Location\s*?:\s*?)(?:https?://|//)?(?:[a-zA-Z0-9\-_\.@]*)oast\.pro.*$/

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

The full check
id: CVE-2023-33405

info:
  name: BlogEngine CMS - Open Redirect
  author: Shankar Acharya
  severity: medium
  description: |
    Blogengine.net 3.3.8.0 and earlier is vulnerable to Open Redirect
  impact: |
    Unauthenticated attackers can exploit open redirect through the years parameter to redirect users to malicious websites for phishing attacks.
  remediation: |
    Update to the latest version of blogengine.net CMS  to fix the open redirect vulnerability.
  reference:
    - https://github.com/hacip/CVE-2023-33405
    - https://nvd.nist.gov/vuln/detail/CVE-2023-33405
    - https://github.com/nomi-sec/PoC-in-GitHub
  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-33405
    cwe-id: CWE-601
    epss-score: 0.31265
    epss-percentile: 0.98288
    cpe: cpe:2.3:a:blogengine:blogengine.net:*:*:*:*:*:*:*:*
  metadata:
    verified: true
    max-request: 1
    vendor: blogengine
    product: blogengine.net
    shodan-query: http.html:"blogengine.net"
    fofa-query: body="blogengine.net"
  tags: cve2023,cve,Blogengine,cms,redirect,blogengine,vuln

http:
  - method: GET
    path:
      - "{{BaseURL}}/default.aspx?years=http://oast.pro"

    matchers:
      - type: regex
        regex:
          - '(?m)^(?:Location\s*?:\s*?)(?:https?://|//)?(?:[a-zA-Z0-9\-_\.@]*)oast\.pro.*$'
        part: header

References

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