{"answers":{"affected":"2 open source packages ship an affected version, including total4. It affects 1 product.","exploited":"There is no known exploitation of CVE-2019-15953 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2019-15953 yet. Limit exposure of the affected software until one is available.","what":"CVE-2019-15953 is a high-severity missing authorization vulnerability in n/a, published on 5 Sep 2019. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2019-15953 and fix it if it is affected.\n\nWhat it is: CVE-2019-15953 is a high-severity missing authorization vulnerability in n/a, published on 5 Sep 2019. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2019-15953 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- total4 (npm): affected all versions; no fix listed\n- total4 (npm): affected all versions; no fix listed\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-2019-15953/ (Markdown: https://insights.sbomify.com/CVE-2019-15953/index.md)","id":"CVE-2019-15953","markdown":"https://insights.sbomify.com/CVE-2019-15953/index.md","name":"CVE-2019-15953","record":{"aliases":["GHSA-q3x9-28f7-w8rc"],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["privilege_escalation","data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Total.js CMS","requires_auth":"low_privilege","summary":"Authenticated users can access unauthorized resources via API requests due to missing authorization checks, leading to privilege escalation.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"total.js_cms","vendor":"totaljs"}],"cvss":{"score":8.8,"severity":"high","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","version":"3.0"},"cwes":[{"id":"CWE-862","name":"Missing Authorization"}],"description":"An issue was discovered in Total.js CMS 12.0.0. An authenticated user with limited privileges can get access to a resource that they do not own by calling the associated API. The product correctly manages privileges only for the front-end resource path, not for API requests. This leads to vertical and horizontal privilege escalation.","ecosystems":["npm"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Total.js CMS Unauthorized Access","id":"CVE-2019-15953","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"missing_authorization","year":"2019"},"n_packages":2,"n_references":2,"next":{"headline":"Total.js CMS RCE Vulnerability","id":"CVE-2019-15954"},"packages":[{"ecosystem":"npm","fixed":[],"introduced":[],"last_affected":[],"package":"total4","purl":null,"source":"GHSA-q3x9-28f7-w8rc"},{"ecosystem":"npm","fixed":[],"introduced":[],"last_affected":[],"package":"total4","purl":"pkg:npm/total4","source":"GHSA-q3x9-28f7-w8rc"}],"prev":{"headline":"Total.js CMS Path Traversal","id":"CVE-2019-15952"},"products":["n/a"],"published":"2019-09-05","related":[{"cvss_score":9.9,"headline":"Total.js CMS RCE Vulnerability","id":"CVE-2019-15954","kev_date_added":null,"published":"2019-09-05"},{"cvss_score":8.8,"headline":"Total.js CMS Path Traversal","id":"CVE-2019-15952","kev_date_added":null,"published":"2019-09-05"},{"cvss_score":7.5,"headline":"Code injection in n/a","id":"CVE-2020-9381","kev_date_added":null,"published":"2020-02-24"},{"cvss_score":6.5,"headline":"Weak cryptography in n/a","id":"CVE-2019-15955","kev_date_added":null,"published":"2019-09-05"},{"cvss_score":6.1,"headline":"Moderate severity vulnerability that affects total.js","id":"CVE-2019-10260","kev_date_added":null,"published":"2019-03-28"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-05","vendors":["n/a"]},"summary":"Authenticated users can access unauthorized resources via API requests due to missing authorization checks, leading to privilege escalation.","url":"https://insights.sbomify.com/CVE-2019-15953/"}