{"answers":{"affected":"","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-50340 exists.","fix":"No fix has been published for CVE-2025-50340 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-50340 is a medium-severity missing authorization vulnerability in n/a, published on 4 Aug 2025. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-50340 and fix it if it is affected.\n\nWhat it is: CVE-2025-50340 is a medium-severity missing authorization vulnerability in n/a, published on 4 Aug 2025. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-50340 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-2025-50340/ (Markdown: https://insights.sbomify.com/CVE-2025-50340/index.md)","id":"CVE-2025-50340","markdown":"https://insights.sbomify.com/CVE-2025-50340/index.md","name":"CVE-2025-50340","record":{"aliases":["GHSA-2397-fjxq-4xvj","UBUNTU-CVE-2025-50340"],"analysis":{"component_type":"web_application","fix_type":"no_fix_stated","impacts":["data_modify","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"SOGo Webmail","requires_auth":"low_privilege","summary":"Authenticated users can send emails as others by manipulating identifiers, enabling impersonation and phishing due to missing sender authorization checks.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[],"cvss":{"score":4.3,"severity":"medium","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-639","name":"Authorization Bypass Through User-Controlled Key"}],"description":"An Insecure Direct Object Reference (IDOR) vulnerability was discovered in SOGo Webmail thru 5.6.0, allowing an authenticated user to send emails on behalf of other users by manipulating a user-controlled identifier in the email-sending request. The server fails to verify whether the authenticated user is authorized to use the specified sender identity, resulting in unauthorized message delivery as another user. This can lead to impersonation, phishing, or unauthorized communication within the system. NOTE: this is disputed by the Supplier because the only effective way to prevent this sender spoofing is on the SMTP server, not within a client such as SOGo.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":"2025-07-31","github_poc":1,"max_poc_stars":0,"metasploit":0,"nuclei":0,"refs":[{"date":"2025-07-31T08:04:53Z","kind":"github_poc","ref":"https://github.com/millad7/SOGo_web_mail-vulnerability-CVE-2025-50340","stars":0,"title":"Insecure Direct Object Reference (IDOR vulnerability) in SOGo Webmail Allows a user to send emails on behalf of  another user. "}],"tier":"weaponised"},"has_fix":false,"headline":"Missing authorization in n/a","id":"CVE-2025-50340","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"missing_authorization","year":"2025"},"n_packages":0,"n_references":4,"next":{"headline":"SQL injection in n/a","id":"CVE-2025-50341"},"packages":[],"prev":{"headline":"Denial of service in n/a","id":"CVE-2025-50334"},"products":["n/a"],"published":"2025-08-04","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"},{"class":"open","licence":"CC0","name":"PoC-in-GitHub"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-08-15","vendors":["n/a"]},"summary":"Authenticated users can send emails as others by manipulating identifiers, enabling impersonation and phishing due to missing sender authorization checks.","url":"https://insights.sbomify.com/CVE-2025-50340/"}