{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2001-1363 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2001-1363 yet. Limit exposure of the affected software until one is available.","what":"CVE-2001-1363 is a critical vulnerability in n/a, published on 11 Jun 2002. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2001-1363 and fix it if it is affected.\n\nWhat it is: CVE-2001-1363 is a critical vulnerability in n/a, published on 11 Jun 2002. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2001-1363 in the wild and no public exploit code.\n\nAffected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2001-1363/ (Markdown: https://insights.sbomify.com/CVE-2001-1363/index.md)","id":"CVE-2001-1363","markdown":"https://insights.sbomify.com/CVE-2001-1363/index.md","name":"CVE-2001-1363","record":{"aliases":["GHSA-qjwr-h3x3-ww46"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["privilege_escalation"],"network_reachable":"yes","non_default_config":true,"product_category":"phpWebSite CMS","requires_auth":"low_privilege","summary":"Attackers can gain administrative privileges in phpWebSite when multiple instances run on the same domain.","user_interaction":"not_required","vuln_class":"privilege_escalation"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"phpwebsite","vendor":"phpwebsite_development_team"}],"cvss":{"score":10,"severity":"critical","source":"nvd","vector":"AV:N/AC:L/Au:N/C:C/I:C/A:C","version":"2.0"},"cwes":[],"description":"Vulnerability in phpWebSite before 0.7.9 related to running multiple instances in the same domain, which may allow attackers to gain administrative privileges.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Privilege escalation in n/a","id":"CVE-2001-1363","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"privilege_escalation","year":"2001"},"n_packages":0,"n_references":2,"next":{"headline":"Vulnerability in autodns.pl for AutoDNS before 0.0.4 related to domain names that are not fully qualified.","id":"CVE-2001-1364"},"packages":[],"prev":{"headline":"Other in n/a","id":"CVE-2001-1362"},"products":["n/a"],"published":"2002-06-11","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-08","vendors":["n/a"]},"summary":"Attackers can gain administrative privileges in phpWebSite when multiple instances run on the same domain.","url":"https://insights.sbomify.com/CVE-2001-1363/"}