{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2018-25093 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2018-25093 yet. Limit exposure of the affected software until one is available.","what":"CVE-2018-25093 is a medium-severity missing authorization vulnerability in Vaerys-Dawn DiscordSailv2, published on 6 Nov 2023. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2018-25093 and fix it if it is affected.\n\nWhat it is: CVE-2018-25093 is a medium-severity missing authorization vulnerability in Vaerys-Dawn DiscordSailv2, published on 6 Nov 2023. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2018-25093 in the wild and no public exploit code.\n\nAffected product: Vaerys-Dawn DiscordSailv2. 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-25093/ (Markdown: https://insights.sbomify.com/CVE-2018-25093/index.md)","id":"CVE-2018-25093","markdown":"https://insights.sbomify.com/CVE-2018-25093/index.md","name":"CVE-2018-25093","record":{"aliases":["GHSA-mvwp-f7w8-54v5"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Discord bot library","requires_auth":"low_privilege","summary":"Attackers can bypass tag access controls in DiscordSailv2, allowing unauthorized actions via the Tag Handler component.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulDB","cpe":[{"product":"discordsailv2","vendor":"vaerys-dawn"}],"cvss":{"score":5.5,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L","version":"3.1"},"cwes":[{"id":"CWE-284","name":"Improper Access Control"}],"description":"A vulnerability was found in Vaerys-Dawn DiscordSailv2 up to 2.10.2. It has been rated as critical. Affected by this issue is some unknown functionality of the component Tag Handler. The manipulation leads to improper access controls. Upgrading to version 2.10.3 is able to address this issue. The name of the patch is cc12e0be82a5d05d9f359ed8e56088f4f8b8eb69. It is recommended to upgrade the affected component. The identifier of this vulnerability is VDB-244484.","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":"Vaerys-Dawn DiscordSailv2 Tag access control","id":"CVE-2018-25093","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"missing_authorization","year":"2018"},"n_packages":0,"n_references":4,"next":{"headline":"ระบบบัญชีออนไลน์ Online Accounting System image.php path traversal","id":"CVE-2018-25094"},"packages":[],"prev":{"headline":"Vaerys-Dawn DiscordSailv2 Command Mention access control","id":"CVE-2018-25092"},"products":["DiscordSailv2"],"published":"2023-11-06","related":[{"cvss_score":5.5,"headline":"Vaerys-Dawn DiscordSailv2 Command Mention access control","id":"CVE-2018-25092","kev_date_added":null,"published":"2023-11-05"}],"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":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2024-08-05","vendors":["Vaerys-Dawn"]},"summary":"Attackers can bypass tag access controls in DiscordSailv2, allowing unauthorized actions via the Tag Handler component.","url":"https://insights.sbomify.com/CVE-2018-25093/"}