{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-4749 exists.","fix":"No fix has been published for CVE-2024-4749 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-4749 is a high-severity cross-site scripting vulnerability in Unknown wp-eMember, published on 4 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-4749 and fix it if it is affected.\n\nWhat it is: CVE-2024-4749 is a high-severity cross-site scripting vulnerability in Unknown wp-eMember, published on 4 Jun 2024. 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-2024-4749 exists.\n\nAffected product: Unknown wp-eMember. 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-4749/ (Markdown: https://insights.sbomify.com/CVE-2024-4749/index.md)","id":"CVE-2024-4749","markdown":"https://insights.sbomify.com/CVE-2024-4749/index.md","name":"CVE-2024-4749","record":{"aliases":["GHSA-4x3h-fqm2-2c9h"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress plugin","requires_auth":"none","summary":"Attackers can execute arbitrary scripts in victim browsers via unsanitized input in the WP eMember plugin.","user_interaction":"not_required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"WPScan","cpe":[{"product":"wp_emember","vendor":"tipsandtricks-hq"}],"cvss":{"score":8.3,"severity":"high","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:L","version":"3.1"},"cwes":[{"id":"CWE-79","name":"Improper Neutralization of Input During Web Page Generation"}],"description":"The wp-eMember WordPress plugin before 10.3.9 does not sanitize and escape the \"fieldId\" parameter before outputting it back in the page, leading to a Reflected Cross-Site Scripting.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":null,"headline":"WP eMember \u003c 10.3.9 - Reflected XSS","id":"CVE-2024-4749","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xss","year":"2024"},"n_packages":0,"n_references":1,"next":{"headline":"BuddyBoss Platform \u003c 2.6.0 - Insecure Direct Object Reference on Like Comment","id":"CVE-2024-4750"},"packages":[],"prev":{"headline":"RCE in Cruddiy","id":"CVE-2024-4748"},"products":["wp-eMember"],"published":"2024-06-04","related":[{"cvss_score":8.8,"headline":"WP eMember \u003c 10.6.6 - Bulk Delete via CSRF","id":"CVE-2024-5076","kev_date_added":null,"published":"2024-07-13"},{"cvss_score":8.8,"headline":"WP eMember \u003c 10.6.6 - Admin+ Arbitrary File Upload","id":"CVE-2024-5080","kev_date_added":null,"published":"2024-07-13"},{"cvss_score":7.1,"headline":"WP eMember \u003c 10.6.7 - Reflected XSS via Member Edit","id":"CVE-2024-5715","kev_date_added":null,"published":"2024-07-13"},{"cvss_score":6.8,"headline":"WP eMember \u003c 10.6.6 - Stored XSS in Blacklist via CSRF","id":"CVE-2024-5077","kev_date_added":null,"published":"2024-07-13"},{"cvss_score":6.8,"headline":"WP eMember \u003c 10.6.7 - Reflected XSS","id":"CVE-2024-5744","kev_date_added":null,"published":"2024-07-13"},{"cvss_score":6.1,"headline":"WP eMember \u003c= v10.7.0 - Stored XSS via CSRF","id":"CVE-2024-5081","kev_date_added":null,"published":"2024-08-05"}],"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":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2024-08-01","vendors":["Unknown"]},"summary":"Attackers can execute arbitrary scripts in victim browsers via unsanitized input in the WP eMember plugin.","url":"https://insights.sbomify.com/CVE-2024-4749/"}