{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2024-8490 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2024-8490 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-8490 is a high-severity vulnerability in propertyhive Property Hive, published on 17 Sep 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2024-8490 and fix it if it is affected.\n\nWhat it is: CVE-2024-8490 is a high-severity vulnerability in propertyhive Property Hive, published on 17 Sep 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2024-8490 in the wild and no public exploit code.\n\nAffected product: propertyhive Property Hive. 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-8490/ (Markdown: https://insights.sbomify.com/CVE-2024-8490/index.md)","id":"CVE-2024-8490","markdown":"https://insights.sbomify.com/CVE-2024-8490/index.md","name":"CVE-2024-8490","record":{"aliases":["GHSA-jmwg-f97v-w7m5"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["account_takeover","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress plugin","requires_auth":"none","summary":"Attackers can trick administrators into changing their account details, potentially leading to account takeover.","user_interaction":"required","vuln_class":"csrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Wordfence","cpe":[{"product":"propertyhive","vendor":"wp-property-hive"}],"cvss":{"score":8.8,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-352","name":"Cross-Site Request Forgery"}],"description":"The PropertyHive plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 2.0.19. This is due to missing or incorrect nonce validation on the 'save_account_details' function. This makes it possible for unauthenticated attackers to edit the name, email address, and password of an administrator account via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.","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":"PropertyHive \u003c= 2.0.19 - Cross-Site Request Forgery via save_account_details","id":"CVE-2024-8490","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"csrf","year":"2024"},"n_packages":0,"n_references":4,"next":{"headline":"This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.","id":"CVE-2024-8491"},"packages":[],"prev":{"headline":"CSRF due to overly permissive CORS headers in modelscope/agentscope","id":"CVE-2024-8489"},"products":["Property Hive"],"published":"2024-09-17","related":[{"cvss_score":8.7,"headline":"WordPress PropertyHive Plugin \u003c= 2.0.5 is vulnerable to PHP Object Injection","id":"CVE-2024-23513","kev_date_added":null,"published":"2024-02-12"},{"cvss_score":7.1,"headline":"WordPress PropertyHive plugin \u003c= 2.0.8 - Reflected Cross Site Scripting (XSS) vulnerability","id":"CVE-2024-29923","kev_date_added":null,"published":"2024-03-27"},{"cvss_score":7.1,"headline":"WordPress PropertyHive Plugin \u003c= 1.5.48 is vulnerable to Cross Site Scripting (XSS)","id":"CVE-2023-22706","kev_date_added":null,"published":"2023-05-15"},{"cvss_score":7.1,"headline":"WordPress PropertyHive Plugin \u003c= 1.5.46 is vulnerable to Cross Site Scripting (XSS)","id":"CVE-2023-29172","kev_date_added":null,"published":"2023-04-07"},{"cvss_score":6.5,"headline":"WordPress PropertyHive plugin \u003c= 2.0.13 - Cross Site Scripting (XSS) vulnerability","id":"CVE-2024-35701","kev_date_added":null,"published":"2024-06-08"},{"cvss_score":6.5,"headline":"WordPress PropertyHive plugin \u003c= 2.0.10 - Cross Site Scripting (XSS) vulnerability","id":"CVE-2024-34381","kev_date_added":null,"published":"2024-05-06"}],"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":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-04-08","vendors":["propertyhive"]},"summary":"Attackers can trick administrators into changing their account details, potentially leading to account takeover.","url":"https://insights.sbomify.com/CVE-2024-8490/"}