{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2024-5149 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2024-5149 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-5149 is a medium-severity vulnerability in themekraft Post Form – Registration Form – Profile Form for User Profiles – Frontend Content Forms for User Submissions (UGC), published on 5 Jun 2024. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2024-5149 and fix it if it is affected.\n\nWhat it is: CVE-2024-5149 is a medium-severity vulnerability in themekraft Post Form – Registration Form – Profile Form for User Profiles – Frontend Content Forms for User Submissions (UGC), published on 5 Jun 2024. 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-2024-5149 in the wild and no public exploit code.\n\nAffected product: themekraft Post Form – Registration Form – Profile Form for User Profiles – Frontend Content Forms for User Submissions (UGC). 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-2024-5149/ (Markdown: https://insights.sbomify.com/CVE-2024-5149/index.md)","id":"CVE-2024-5149","markdown":"https://insights.sbomify.com/CVE-2024-5149/index.md","name":"CVE-2024-5149","record":{"aliases":["GHSA-xfjh-8mwq-67xv"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress plugin","requires_auth":"none","summary":"Unauthenticated attackers can bypass email verification in BuddyForms due to weak activation codes, allowing unauthorized access to verified features.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Wordfence","cpe":[{"product":"buddyforms","vendor":"themekraft"}],"cvss":{"score":6.5,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-330","name":"Use of Insufficiently Random Values"}],"description":"The BuddyForms plugin for WordPress is vulnerable to Email Verification Bypass in all versions up to, and including, 2.8.9 via the use of an insufficiently random activation code. This makes it possible for unauthenticated attackers to bypass the email verification.","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":"BuddyForms \u003c= 2.8.9 - Email Verification Bypass due to Insufficient Randomness","id":"CVE-2024-5149","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"security_feature_bypass","year":"2024"},"n_packages":0,"n_references":3,"next":{"headline":"Login with phone number \u003c= 1.7.26 - Authentication Bypass due to Missing Empty Value Check","id":"CVE-2024-5150"},"packages":[],"prev":{"headline":"Gnome-remote-desktop: inadequate validation of session agents using d-bus methods may expose rdp tls certificate","id":"CVE-2024-5148"},"products":["Post Form – Registration Form – Profile Form for User Profiles – Frontend Content Forms for User Submissions (UGC)"],"published":"2024-06-05","related":[{"cvss_score":9.8,"headline":"Deserialization in BuddyForms WordPress Plugin","id":"CVE-2023-26326","kev_date_added":null,"published":"2023-02-23"},{"cvss_score":9.8,"headline":"SQL injection in n/a","id":"CVE-2018-21003","kev_date_added":null,"published":"2019-08-27"},{"cvss_score":8.8,"headline":"Privilege escalation in Post Form – Registration Form – Profile Form for User Profiles – Frontend Content Forms for User Submissions (UGC)","id":"CVE-2024-8246","kev_date_added":null,"published":"2024-09-14"},{"cvss_score":8.6,"headline":"WordPress buddyforms plugin \u003c= 2.8.8- Arbitrary File Read and SSRF vulnerability","id":"CVE-2024-32830","kev_date_added":null,"published":"2024-05-17"},{"cvss_score":7.5,"headline":"WordPress BuddyForms plugin \u003c= 2.10.2 - Local File Inclusion vulnerability","id":"CVE-2025-32151","kev_date_added":null,"published":"2025-04-04"},{"cvss_score":6.4,"headline":"Cross-site scripting in Post Form – Registration Form – Profile Form for User Profiles – Frontend Content Forms for User Submissions (UGC)","id":"CVE-2024-12038","kev_date_added":null,"published":"2025-02-22"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"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":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-04-08","vendors":["themekraft"]},"summary":"Unauthenticated attackers can bypass email verification in BuddyForms due to weak activation codes, allowing unauthorized access to verified features.","url":"https://insights.sbomify.com/CVE-2024-5149/"}