{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2018-19110 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2018-19110 yet. Limit exposure of the affected software until one is available.","what":"CVE-2018-19110 is a medium-severity missing authorization vulnerability in n/a, published on 8 Nov 2018. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2018-19110 and fix it if it is affected.\n\nWhat it is: CVE-2018-19110 is a medium-severity missing authorization vulnerability in n/a, published on 8 Nov 2018. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2018-19110 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-2018-19110/ (Markdown: https://insights.sbomify.com/CVE-2018-19110/index.md)","id":"CVE-2018-19110","markdown":"https://insights.sbomify.com/CVE-2018-19110/index.md","name":"CVE-2018-19110","record":{"aliases":["GHSA-3wmg-53g4-p9v4"],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Tianti CMS","requires_auth":"low_privilege","summary":"Authenticated users can bypass permission restrictions to access skin management features due to missing authorization checks in the controller.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"tianti","vendor":"tianti_project"}],"cvss":{"score":6.5,"severity":"medium","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N","version":"3.0"},"cwes":[{"id":"CWE-862","name":"Missing Authorization"}],"description":"The skin-management feature in tianti 2.3 allows remote authenticated users to bypass intended permission restrictions by visiting tianti-module-admin/user/skin/list directly because controller\\usercontroller.java maps a /skin/list request to the function skinList, and lacks an authorization check.","ecosystems":[],"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":"Missing authorization in n/a","id":"CVE-2018-19110","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"missing_authorization","year":"2018"},"n_packages":0,"n_references":1,"next":{"headline":"Information disclosure in n/a","id":"CVE-2018-19111"},"packages":[],"prev":{"headline":"Missing authorization in n/a","id":"CVE-2018-19109"},"products":["n/a"],"published":"2018-11-08","related":[{"cvss_score":8.8,"headline":"Cross-site request forgery in n/a","id":"CVE-2025-25907","kev_date_added":null,"published":"2025-03-10"},{"cvss_score":8.8,"headline":"Missing authorization in n/a","id":"CVE-2018-19109","kev_date_added":null,"published":"2018-11-08"},{"cvss_score":8,"headline":"Cross-site request forgery in n/a","id":"CVE-2025-27910","kev_date_added":null,"published":"2025-03-10"},{"cvss_score":5.4,"headline":"Cross-site scripting in n/a","id":"CVE-2025-25908","kev_date_added":null,"published":"2025-03-10"},{"cvss_score":5.4,"headline":"Cross-site scripting in n/a","id":"CVE-2018-19089","kev_date_added":null,"published":"2018-11-07"},{"cvss_score":5.4,"headline":"Cross-site scripting in n/a","id":"CVE-2018-19090","kev_date_added":null,"published":"2018-11-07"}],"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":"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 bypass permission restrictions to access skin management features due to missing authorization checks in the controller.","url":"https://insights.sbomify.com/CVE-2018-19110/"}