{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2022-1239 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2022-1239 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-1239 is a high-severity server-side request forgery vulnerability in Unknown HubSpot – CRM, Email Marketing, Live Chat, Forms \u0026 Analytics, published on 2 May 2022. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2022-1239 and fix it if it is affected.\n\nWhat it is: CVE-2022-1239 is a high-severity server-side request forgery vulnerability in Unknown HubSpot – CRM, Email Marketing, Live Chat, Forms \u0026 Analytics, published on 2 May 2022. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2022-1239 in the wild and no public exploit code.\n\nAffected product: Unknown HubSpot – CRM, Email Marketing, Live Chat, Forms \u0026 Analytics. 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-2022-1239/ (Markdown: https://insights.sbomify.com/CVE-2022-1239/index.md)","id":"CVE-2022-1239","markdown":"https://insights.sbomify.com/CVE-2022-1239/index.md","name":"CVE-2022-1239","record":{"aliases":["GHSA-mqqr-fmxw-ghxx"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"HubSpot WordPress plugin","requires_auth":"low_privilege","summary":"Contributors can exploit a lack of validation in the proxy endpoint to perform Server-Side Request Forgery attacks against internal resources.","user_interaction":"not_required","vuln_class":"ssrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"WPScan","cpe":[{"product":"hubspot","vendor":"hubspot"}],"cvss":{"score":8.8,"severity":"high","source":"nvd","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-918","name":"Server-Side Request Forgery"}],"description":"The HubSpot WordPress plugin before 8.8.15 does not validate the proxy URL given to the proxy REST endpoint, which could allow users with the edit_posts capability (by default contributor and above) to perform SSRF attacks","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":"HubSpot \u003c 8.8.15 - Contributor+ Blind SSRF","id":"CVE-2022-1239","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"ssrf","year":"2022"},"n_packages":0,"n_references":1,"next":{"headline":"Heap buffer overflow in libr/bin/format/mach0/mach0.c in radareorg/radare2","id":"CVE-2022-1240"},"packages":[],"prev":{"headline":"Out-of-bounds Write in libr/bin/format/ne/ne.c in radareorg/radare2","id":"CVE-2022-1238"},"products":["HubSpot – CRM, Email Marketing, Live Chat, Forms \u0026 Analytics"],"published":"2022-05-02","related":[{"cvss_score":6.4,"headline":"Cross-site scripting in HubSpot All-In-One Marketing – Forms, Popups, Live Chat","id":"CVE-2024-5879","kev_date_added":null,"published":"2024-08-30"}],"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":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-02","vendors":["Unknown"]},"summary":"Contributors can exploit a lack of validation in the proxy endpoint to perform Server-Side Request Forgery attacks against internal resources.","url":"https://insights.sbomify.com/CVE-2022-1239/"}