{"answers":{"affected":"2 open source packages ship an affected version, including s9y/serendipity. It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-39971 exists.","fix":"Upgrade s9y/serendipity to 2.6.0 or later.","what":"CVE-2026-39971 is a high-severity vulnerability in S9y Serendipity, published on 14 Apr 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-39971 and fix it if it is affected.\n\nWhat it is: CVE-2026-39971 is a high-severity vulnerability in S9y Serendipity, published on 14 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-39971 exists.\n\nAffected packages and fixed versions:\n- s9y/serendipity (Packagist): affected all versions; fixed in 2.6.0\n- s9y/serendipity (Packagist): affected all versions; fixed in 2.6.0\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-39971/ (Markdown: https://insights.sbomify.com/CVE-2026-39971/index.md)","id":"CVE-2026-39971","markdown":"https://insights.sbomify.com/CVE-2026-39971/index.md","name":"CVE-2026-39971","record":{"aliases":["GHSA-458g-q4fh-mj6r"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_modify","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"PHP weblog engine","requires_auth":"none","summary":"Attackers can inject SMTP headers via Host header manipulation in Serendipity, enabling email spoofing and reply hijacking.","user_interaction":"not_required","vuln_class":"other"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"serendipity","vendor":"s9y"}],"cvss":{"score":7.2,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-113","name":"Improper Neutralization of CRLF Sequences in HTTP Headers"}],"description":"Serendipity is a PHP-powered weblog engine. In versions 2.6-beta2 and below, the email sending functionality in include/functions.inc.php inserts $_SERVER['HTTP_HOST'] directly into the Message-ID SMTP header without validation, and the existing sanitization function serendipity_isResponseClean() is not called on HTTP_HOST before embedding it. An attacker who can control the Host header during an email-triggering action such as comment notifications or subscription emails can inject arbitrary SMTP headers into outgoing emails. This enables identity spoofing, reply hijacking via manipulated Message-ID threading, and email reputation abuse through the attacker's domain being embedded in legitimate mail headers. This issue has been fixed in version 2.6.0.","ecosystems":["Packagist"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":true,"headline":"Serendipity: Host Header Injection leads to SMTP header injection via unvalidated HTTP_HOST","id":"CVE-2026-39971","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Packagist","product":"s9y:serendipity","products":["s9y:serendipity"],"type":"other","year":"2026"},"n_packages":2,"n_references":2,"next":{"headline":"Mercure has a Topic Selector Cache Key Collision","id":"CVE-2026-39972"},"packages":[{"ecosystem":"Packagist","fixed":["2.6.0"],"introduced":["0"],"last_affected":[],"package":"s9y/serendipity","purl":null,"source":"GHSA-458g-q4fh-mj6r"},{"ecosystem":"Packagist","fixed":["2.6.0"],"introduced":["0"],"last_affected":[],"package":"s9y/serendipity","purl":"pkg:composer/s9y/serendipity","source":"GHSA-458g-q4fh-mj6r"}],"prev":{"headline":"TypeBot: Stored Cross-Site Scripting (XSS) via SVG File Upload On Profile Picture Form","id":"CVE-2026-39970"},"products":["Serendipity"],"published":"2026-04-14","related":[{"cvss_score":10,"headline":"Other in n/a","id":"CVE-2005-1449","kev_date_added":null,"published":"2005-05-03"},{"cvss_score":10,"headline":"Missing authorization in n/a","id":"CVE-2005-1452","kev_date_added":null,"published":"2005-05-03"},{"cvss_score":9.8,"headline":"File upload in n/a","id":"CVE-2020-10964","kev_date_added":null,"published":"2020-03-25"},{"cvss_score":9.8,"headline":"Cross-site scripting in n/a","id":"CVE-2011-1134","kev_date_added":null,"published":"2019-11-05"},{"cvss_score":9.8,"headline":"File upload in n/a","id":"CVE-2016-10752","kev_date_added":null,"published":"2019-05-24"},{"cvss_score":9.8,"headline":"Code injection in n/a","id":"CVE-2016-10082","kev_date_added":null,"published":"2016-12-30"},{"cvss_score":8.8,"headline":"File upload in n/a","id":"CVE-2023-31576","kev_date_added":null,"published":"2023-05-16"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"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":"yes","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-04-15","vendors":["s9y"]},"summary":"Attackers can inject SMTP headers via Host header manipulation in Serendipity, enabling email spoofing and reply hijacking.","url":"https://insights.sbomify.com/CVE-2026-39971/"}