{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-45125 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-45125 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-45125 is a medium-severity vulnerability in mybb, published on 18 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-45125 and fix it if it is affected.\n\nWhat it is: CVE-2026-45125 is a medium-severity vulnerability in mybb, published on 18 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-45125 in the wild and no public exploit code.\n\nAffected product: mybb. 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-2026-45125/ (Markdown: https://insights.sbomify.com/CVE-2026-45125/index.md)","id":"CVE-2026-45125","markdown":"https://insights.sbomify.com/CVE-2026-45125/index.md","name":"CVE-2026-45125","record":{"aliases":["GHSA-f626-53q9-pqm9"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_modify","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"MyBB forum software","requires_auth":"none","summary":"Attackers can inject arbitrary mail headers via CRLF sequences in the Email User feature, potentially spoofing sender details or manipulating email routing.","user_interaction":"not_required","vuln_class":"other"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":5.3,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-93","name":"Improper Neutralization of CRLF Sequences"}],"description":"MyBB is free and open source forum software. Prior to 1.8.40, the Email User controller does not sanitize sender names correctly, resulting in mail header injection. member.php?action=do_emailuser accepts the fromname HTTP parameter for guests or the stored username for authenticated users when the cansendemail group permission is enabled. When mail_handler is set to the default PHP mail value, the sender name is used without sanitization in Return-Path and Reply-To headers, allowing arbitrary headers to be injected with CRLF sequences. This issue is fixed in version 1.8.40.","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":"MyBB: Email User CRLF injection","id":"CVE-2026-45125","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"other","year":"2026"},"n_packages":0,"n_references":4,"next":{"headline":"MyBB: ACP Questions state CSRF","id":"CVE-2026-45126"},"packages":[],"prev":{"headline":"MyBB: Mod CP report resolution missing authorization","id":"CVE-2026-45124"},"products":["mybb"],"published":"2026-08-18","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)"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-08-18","vendors":["mybb"]},"summary":"Attackers can inject arbitrary mail headers via CRLF sequences in the Email User feature, potentially spoofing sender details or manipulating email routing.","url":"https://insights.sbomify.com/CVE-2026-45125/"}