{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2003-1213 exists.","fix":"No fix has been published for CVE-2003-1213 yet. Limit exposure of the affected software until one is available.","what":"CVE-2003-1213 is a high-severity vulnerability in n/a, published on 19 May 2005. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2003-1213 and fix it if it is affected.\n\nWhat it is: CVE-2003-1213 is a high-severity vulnerability in n/a, published on 19 May 2005. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2003-1213 exists.\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-2003-1213/ (Markdown: https://insights.sbomify.com/CVE-2003-1213/index.md)","id":"CVE-2003-1213","markdown":"https://insights.sbomify.com/CVE-2003-1213/index.md","name":"CVE-2003-1213","record":{"aliases":["GHSA-xj39-j4c9-rmv6"],"analysis":{"component_type":"web_application","fix_type":"configuration_change","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"MaxWebPortal","requires_auth":"none","summary":"Remote attackers can access sensitive database information by directly requesting the exposed database file in the default installation.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"maxwebportal","vendor":"maxwebportal"}],"cvss":{"score":7.5,"severity":"high","source":"nvd","vector":"AV:N/AC:L/Au:N/C:P/I:P/A:P","version":"2.0"},"cwes":[],"description":"The default installation of MaxWebPortal 1.30 stores the portal database under the web document root with insecure access control, which allows remote attackers to obtain sensitive information via a direct request to database/db2000.mdb.","ecosystems":[],"exploits":{"exploitdb":1,"first_seen":"2003-06-06","github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[{"date":"2003-06-06","kind":"exploitdb","ref":"22747","stars":null,"title":"Maxwebportal 1.30 - Remote Database Disclosure"}],"tier":"weaponised"},"has_fix":null,"headline":"Information disclosure in n/a","id":"CVE-2003-1213","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2003"},"n_packages":0,"n_references":4,"next":{"headline":"Auth bypass in n/a","id":"CVE-2003-1214"},"packages":[],"prev":{"headline":"Missing authorization in n/a","id":"CVE-2003-1212"},"products":["n/a"],"published":"2005-05-19","related":[{"cvss_score":7.5,"headline":"SQL injection in n/a","id":"CVE-2009-3436","kev_date_added":null,"published":"2009-09-28"},{"cvss_score":7.5,"headline":"SQL injection in n/a","id":"CVE-2005-1779","kev_date_added":null,"published":"2005-05-31"},{"cvss_score":7.5,"headline":"SQL injection in n/a","id":"CVE-2005-1562","kev_date_added":null,"published":"2005-05-14"},{"cvss_score":7.5,"headline":"SQL injection in n/a","id":"CVE-2005-1417","kev_date_added":null,"published":"2005-05-03"},{"cvss_score":7.5,"headline":"SQL injection in n/a","id":"CVE-2005-1017","kev_date_added":null,"published":"2005-04-08"},{"cvss_score":7.5,"headline":"SQL injection in n/a","id":"CVE-2004-0272","kev_date_added":null,"published":"2004-03-18"}],"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)"},{"class":"attribution","licence":"GPL-2.0-or-later","name":"Exploit-DB"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-08","vendors":["n/a"]},"summary":"Remote attackers can access sensitive database information by directly requesting the exposed database file in the default installation.","url":"https://insights.sbomify.com/CVE-2003-1213/"}