Viewing Collection: web_static_analysis_normalization

69dba1646c75dc796642791c

Sun Apr 12 2026 13:43:00 GMT+0000 (Coordinated Universal Time)

https://www.mahaonline.gov.in/

normalization

69dba30a472713a39c6d1d35

Sun Apr 12 2026 13:50:02 GMT+0000 (Coordinated Universal Time)

https://www.mahaonline.gov.in/

normalization

69dcce058341da9cc4c7b79a

Mon Apr 13 2026 11:05:41 GMT+0000 (Coordinated Universal Time)

https://cerebralzip.com/

normalization

{
  "unified": [],
  "summary": {
    "domain": "cerebralzip.com",
    "total_after_cleaning": 0,
    "categories": {}
  }
}

69dcce338eb051baf53d2333

Mon Apr 13 2026 11:06:27 GMT+0000 (Coordinated Universal Time)

https://cp-club-vjti.vercel.app/

normalization

{
  "unified": [],
  "summary": {
    "domain": "cp-club-vjti.vercel.app",
    "total_after_cleaning": 0,
    "categories": {}
  }
}

69dcd10f7f2579b6ed9f3b4f

Mon Apr 13 2026 11:18:39 GMT+0000 (Coordinated Universal Time)

https://cp-club-vjti.vercel.app/

normalization

{
  "dynamic_analysis": [
    {
      "title": "Cross-origin resource sharing",
      "raw_title": "1. Cross-origin resource sharing",
      "anchor_id": "1",
      "reference_url": "https://portswigger.net/knowledgebase/issues/details/00200600_crossoriginresourcesharing",
      "summary": {
        "Severity": "Information",
        "Confidence": "Certain",
        "Host": "https://cp-club-vjti.vercel.app",
        "Path": "/robots.txt"
      },
      "details": {
        "Issue detail": "The application implements an HTML5 cross-origin resource sharing (CORS) policy for this request.\nIf the application relies on network firewalls or other IP-based access controls, this policy is likely to present a security risk.\nSince the Vary: Origin header was not present in the response, reverse proxies and intermediate servers may cache it. This may enable an attacker to carry out cache poisoning attacks.",
        "Issue background": "An HTML5 cross-origin resource sharing (CORS) policy controls whether and how content running on other domains can perform two-way interaction with the domain that publishes the policy. The policy is fine-grained and can apply access controls per-request based on the URL and other features of the request.\nIf another domain is allowed by the policy, then that domain can potentially attack users of the application. If a user is logged in to the application, and visits a domain allowed by the policy, then any malicious content running on that domain can potentially retrieve content from the application, and sometimes carry out actions within the security context of the logged in user.\n\nEven if an allowed domain is not overtly malicious in itself, security vulnerabilities within that domain could potentially be leveraged by an attacker to exploit the trust relationship and attack the application that allows access. CORS policies on pages containing sensitive information should be reviewed to determine whether it is appropriate for the application to trust both the intentions and security posture of any domains granted access.",
        "Issue remediation": "Any inappropriate domains should be removed from the CORS policy.",
        "References": [
          {
            "text": "Web Security Academy: Cross-origin resource sharing (CORS)",
            "href": "https://portswigger.net/web-security/cors"
          },
          {
            "text": "Exploiting CORS Misconfigurations",
            "href": "https://portswigger.net/research/exploiting-cors-misconfigurations-for-bitcoins-and-bounties"
          }
        ],
        "Vulnerability classifications": [
          {
            "text": "CWE-942: Overly Permissive Cross-domain Whitelist",
            "href": "https://cwe.mitre.org/data/definitions/942.html"
          }
        ]
      },
      "category": "dynamic_analysis"
    }
  ],
  "unified": [
    {
      "title": "Cross-origin resource sharing",
      "raw_title": "1. Cross-origin resource sharing",
      "anchor_id": "1",
      "reference_url": "https://portswigger.net/knowledgebase/issues/details/00200600_crossoriginresourcesharing",
      "summary": {
        "Severity": "Information",
        "Confidence": "Certain",
        "Host": "https://cp-club-vjti.vercel.app",
        "Path": "/robots.txt"
      },
      "details": {
        "Issue detail": "The application implements an HTML5 cross-origin resource sharing (CORS) policy for this request.\nIf the application relies on network firewalls or other IP-based access controls, this policy is likely to present a security risk.\nSince the Vary: Origin header was not present in the response, reverse proxies and intermediate servers may cache it. This may enable an attacker to carry out cache poisoning attacks.",
        "Issue background": "An HTML5 cross-origin resource sharing (CORS) policy controls whether and how content running on other domains can perform two-way interaction with the domain that publishes the policy. The policy is fine-grained and can apply access controls per-request based on the URL and other features of the request.\nIf another domain is allowed by the policy, then that domain can potentially attack users of the application. If a user is logged in to the application, and visits a domain allowed by the policy, then any malicious content running on that domain can potentially retrieve content from the application, and sometimes carry out actions within the security context of the logged in user.\n\nEven if an allowed domain is not overtly malicious in itself, security vulnerabilities within that domain could potentially be leveraged by an attacker to exploit the trust relationship and attack the application that allows access. CORS policies on pages containing sensitive information should be reviewed to determine whether it is appropriate for the application to trust both the intentions and security posture of any domains granted access.",
        "Issue remediation": "Any inappropriate domains should be removed from the CORS policy.",
        "References": [
          {
            "text": "Web Security Academy: Cross-origin resource sharing (CORS)",
            "href": "https://portswigger.net/web-security/cors"
          },
          {
            "text": "Exploiting CORS Misconfigurations",
            "href": "https://portswigger.net/research/exploiting-cors-misconfigurations-for-bitcoins-and-bounties"
          }
        ],
        "Vulnerability classifications": [
          {
            "text": "CWE-942: Overly Permissive Cross-domain Whitelist",
            "href": "https://cwe.mitre.org/data/definitions/942.html"
          }
        ]
      },
      "category": "dynamic_analysis"
    }
  ],
  "summary": {
    "domain": "cp-club-vjti.vercel.app",
    "total_after_cleaning": 1,
    "categories": {
      "dynamic_analysis": 1
    }
  }
}

69dcd3a135bdbdd6ee8c2209

Mon Apr 13 2026 11:29:37 GMT+0000 (Coordinated Universal Time)

https://www.vjti.ac.in

normalization

{
  "unified": [],
  "summary": {
    "domain": "www.vjti.ac.in",
    "total_after_cleaning": 0,
    "categories": {}
  }
}

69dcd3ab8f5edd4642809907

Mon Apr 13 2026 11:29:47 GMT+0000 (Coordinated Universal Time)

https://vjti.ac.in

normalization

{
  "unified": [],
  "summary": {
    "domain": "vjti.ac.in",
    "total_after_cleaning": 0,
    "categories": {}
  }
}

69dcd3d74cfb58739924c8fc

Mon Apr 13 2026 11:30:31 GMT+0000 (Coordinated Universal Time)

https://vjti.ac.in/

normalization

{
  "unified": [],
  "summary": {
    "domain": "vjti.ac.in",
    "total_after_cleaning": 0,
    "categories": {}
  }
}

69dcd5782133df2d646fff90

Mon Apr 13 2026 11:37:28 GMT+0000 (Coordinated Universal Time)

https://gujaratindia.gov.in/Index

normalization

69dce51dae8cf167e0239ad5

Mon Apr 13 2026 12:44:13 GMT+0000 (Coordinated Universal Time)

https://vjti.ac.in

normalization

{
  "unified": [],
  "summary": {
    "domain": "vjti.ac.in",
    "total_after_cleaning": 0,
    "categories": {}
  }
}