{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-9102 exists.","fix":"No fix has been published for CVE-2025-9102 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-9102 is a medium-severity missing authorization vulnerability in 1\u00261 Mail \u0026 Media mail.com App, published on 18 Aug 2025. 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-2025-9102 and fix it if it is affected.\n\nWhat it is: CVE-2025-9102 is a medium-severity missing authorization vulnerability in 1\u00261 Mail \u0026 Media mail.com App, published on 18 Aug 2025. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-9102 exists.\n\nAffected product: 1\u00261 Mail \u0026 Media mail.com App. 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-2025-9102/ (Markdown: https://insights.sbomify.com/CVE-2025-9102/index.md)","id":"CVE-2025-9102","markdown":"https://insights.sbomify.com/CVE-2025-9102/index.md","name":"CVE-2025-9102","record":{"aliases":["GHSA-c3v6-6xr7-wxj8"],"analysis":{"component_type":"mobile_application","fix_type":"no_fix_stated","impacts":["security_bypass"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"mail.com Android app","requires_auth":"low_privilege","summary":"Improper export of Android components in the mail.com app allows local attackers to bypass security restrictions and access protected functionality.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulDB","cpe":[{"product":"mail.com","vendor":"mail"}],"cvss":{"score":4.8,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P","version":"4.0"},"cwes":[{"id":"CWE-926","name":"Improper Export of Android Application Components"}],"description":"A security vulnerability has been detected in 1\u00261 Mail \u0026 Media mail.com App 8.8.0 on Android. Affected is an unknown function of the file AndroidManifest.xml of the component com.mail.mobile.android.mail. The manipulation leads to improper export of android application components. It is possible to launch the attack on the local host. The exploit has been disclosed to the public and may be used. The vendor was contacted early about this disclosure but did not respond in any way.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":null,"headline":"Missing authorization in mail.com App","id":"CVE-2025-9102","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"missing_authorization","year":"2025"},"n_packages":0,"n_references":5,"next":{"headline":"ZenCart CKEditor cross site scripting","id":"CVE-2025-9103"},"packages":[],"prev":{"headline":"zhenfeng13 My-Blog Tag save cross site scripting","id":"CVE-2025-9101"},"products":["mail.com App"],"published":"2025-08-18","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":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-08-18","vendors":["1\u00261 Mail \u0026 Media"]},"summary":"Improper export of Android components in the mail.com app allows local attackers to bypass security restrictions and access protected functionality.","url":"https://insights.sbomify.com/CVE-2025-9102/"}