{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-5127 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-5127 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-5127 is a high-severity unsafe deserialization vulnerability in wedevs User Frontend: AI Powered Frontend Posting, User Directory, Profile, Membership \u0026 User Registration, published on 8 May 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-5127 and fix it if it is affected.\n\nWhat it is: CVE-2026-5127 is a high-severity unsafe deserialization vulnerability in wedevs User Frontend: AI Powered Frontend Posting, User Directory, Profile, Membership \u0026 User Registration, published on 8 May 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-5127 in the wild and no public exploit code.\n\nAffected product: wedevs User Frontend: AI Powered Frontend Posting, User Directory, Profile, Membership \u0026 User Registration. 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-5127/ (Markdown: https://insights.sbomify.com/CVE-2026-5127/index.md)","id":"CVE-2026-5127","markdown":"https://insights.sbomify.com/CVE-2026-5127/index.md","name":"CVE-2026-5127","record":{"aliases":["GHSA-jc25-ggg4-hhvw"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["code_execution","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress plugin","requires_auth":"low_privilege","summary":"Authenticated attackers can inject PHP objects via the wpuf_files parameter to execute code or delete files if a POP chain exists.","user_interaction":"not_required","vuln_class":"deserialization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Wordfence","cpe":[],"cvss":{"score":8.8,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-502","name":"Deserialization of Untrusted Data"}],"description":"The User Frontend: AI Powered Frontend Posting, User Directory, Profile, Membership \u0026 User Registration plugin for WordPress is vulnerable to Deserialization of Untrusted Data in versions up to, and including, 4.3.1 This is due to insufficient input validation and type checking on the wpuf_files parameter during form submission, combined with unconditional deserialization via maybe_unserialize() when displaying post content. This makes it possible for authenticated attackers, with Subscriber-level access and above, to inject arbitrary PHP objects, which can be leveraged to execute arbitrary code, delete arbitrary files, or perform other malicious actions if a POP chain is present on the target system.","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":"Deserialization in User Frontend: AI Powered Frontend Posting, User Directory, Profile, Membership \u0026 User Registration","id":"CVE-2026-5127","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"deserialization","year":"2026"},"n_packages":0,"n_references":19,"next":{"headline":"This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.","id":"CVE-2026-5128"},"packages":[],"prev":{"headline":"SourceCodester RSS Feed Parser file_get_contents server-side request forgery","id":"CVE-2026-5126"},"products":["User Frontend: AI Powered Frontend Posting, User Directory, Profile, Membership \u0026 User Registration"],"published":"2026-05-08","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":"total"},"state":"PUBLISHED","updated":"2026-05-08","vendors":["wedevs"]},"summary":"Authenticated attackers can inject PHP objects via the wpuf_files parameter to execute code or delete files if a POP chain exists.","url":"https://insights.sbomify.com/CVE-2026-5127/"}