{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2025-8871 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-8871 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-8871 is a medium-severity unsafe deserialization vulnerability in WPEverest Everest Forms Pro, published on 5 Nov 2025. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-8871 and fix it if it is affected.\n\nWhat it is: CVE-2025-8871 is a medium-severity unsafe deserialization vulnerability in WPEverest Everest Forms Pro, published on 5 Nov 2025. 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-2025-8871 in the wild and no public exploit code.\n\nAffected product: WPEverest Everest Forms Pro. 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-8871/ (Markdown: https://insights.sbomify.com/CVE-2025-8871/index.md)","id":"CVE-2025-8871","markdown":"https://insights.sbomify.com/CVE-2025-8871/index.md","name":"CVE-2025-8871","record":{"aliases":["GHSA-6wgh-rvcx-89g9"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["code_execution","data_read","data_modify"],"network_reachable":"yes","non_default_config":true,"product_category":"WordPress plugin","requires_auth":"none","summary":"Unauthenticated attackers can inject PHP objects via PHAR deserialization in Everest Forms Pro, potentially leading to code execution or data theft if a POP chain exists.","user_interaction":"not_required","vuln_class":"deserialization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Wordfence","cpe":[],"cvss":{"score":5.6,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:L","version":"3.1"},"cwes":[{"id":"CWE-502","name":"Deserialization of Untrusted Data"}],"description":"The Everest Forms (Pro) plugin for WordPress is vulnerable to PHP Object Injection in all versions up to, and including, 1.9.7 via deserialization of untrusted input in the mime_content_type() function. This makes it possible for unauthenticated attackers to inject a PHP Object. This vulnerability may be exploited by unauthenticated attackers when a form is present on the site with a non-required signature form field along with an image upload field. No known POP chain is present in the vulnerable software, which means this vulnerability has no impact unless another plugin or theme containing a POP chain is installed on the site. If a POP chain is present via an additional plugin or theme installed on the target system, it may allow the attacker to perform actions like delete arbitrary files, retrieve sensitive data, or execute code depending on the POP chain present. This vulnerability is only exploitable in PHP versions prior to 8.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Everest Forms (Pro) \u003c= 1.9.7 - Unauthenticated PHP Object Injection via PHAR Deserialization in Form Signature","id":"CVE-2025-8871","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"deserialization","year":"2025"},"n_packages":0,"n_references":2,"next":{"headline":"Denial of service in EOS","id":"CVE-2025-8872"},"packages":[],"prev":{"headline":"Denial of service in EOS","id":"CVE-2025-8870"},"products":["Everest Forms Pro"],"published":"2025-11-05","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":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-04-08","vendors":["WPEverest"]},"summary":"Unauthenticated attackers can inject PHP objects via PHAR deserialization in Everest Forms Pro, potentially leading to code execution or data theft if a POP chain exists.","url":"https://insights.sbomify.com/CVE-2025-8871/"}