{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2024-37118 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2024-37118 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-37118 is a medium-severity vulnerability in Uncanny Automator Pro, published on 21 Jun 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-37118 and fix it if it is affected.\n\nWhat it is: CVE-2024-37118 is a medium-severity vulnerability in Uncanny Automator Pro, published on 21 Jun 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-37118 in the wild and no public exploit code.\n\nAffected product: Uncanny Automator Pro. 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-37118/ (Markdown: https://insights.sbomify.com/CVE-2024-37118/index.md)","id":"CVE-2024-37118","markdown":"https://insights.sbomify.com/CVE-2024-37118/index.md","name":"CVE-2024-37118","record":{"aliases":["GHSA-6g2q-m7q5-4w3c"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress plugin","requires_auth":"none","summary":"An attacker can trick a logged-in admin into resetting license settings in the Uncanny Automator Pro WordPress plugin via CSRF.","user_interaction":"required","vuln_class":"csrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Patchstack","cpe":[{"product":"uncanny_automator","vendor":"uncannyowl"}],"cvss":{"score":5.4,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:L","version":"3.1"},"cwes":[{"id":"CWE-352","name":"Cross-Site Request Forgery"}],"description":"Cross Site Request Forgery (CSRF) vulnerability in Uncanny Owl Uncanny Automator Pro.This issue affects Uncanny Automator Pro: from n/a through 5.3.","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":"Cross-site request forgery in Uncanny Automator Pro","id":"CVE-2024-37118","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"csrf","year":"2024"},"n_packages":0,"n_references":1,"next":{"headline":"WordPress Uncanny Automator Pro plugin \u003c 5.3.0.1 - Unauthenticated License Settings Reset vulnerability","id":"CVE-2024-37119"},"packages":[],"prev":{"headline":"WordPress Uncanny Automator Pro plugin \u003c= 5.3 - Reflected Cross Site Scripting (XSS) vulnerability","id":"CVE-2024-37117"},"products":["Uncanny Automator Pro"],"published":"2024-06-21","related":[{"cvss_score":9.1,"headline":"Uncanny Automator \u003c= 6.4.0.1 - Unauthenticated PHP Object Injection in automator_api_decode_message Function","id":"CVE-2025-3623","kev_date_added":null,"published":"2025-05-14"},{"cvss_score":8.8,"headline":"Uncanny Automator \u003c= 6.3.0.2 - Missing Authorization to Authenticated (Subscriber+) Privilege Escalation","id":"CVE-2025-2075","kev_date_added":null,"published":"2025-04-04"},{"cvss_score":7.1,"headline":"WordPress Uncanny Automator Pro plugin \u003c= 5.3 - Reflected Cross Site Scripting (XSS) vulnerability","id":"CVE-2024-37117","kev_date_added":null,"published":"2024-07-22"},{"cvss_score":6.5,"headline":"WordPress Uncanny Automator plugin \u003c= 6.4.0.2 - Broken Access Control Vulnerability","id":"CVE-2025-48133","kev_date_added":null,"published":"2025-06-05"},{"cvss_score":5.5,"headline":"Server-side request forgery in Uncanny Automator – Easy Automation, Integration, Webhooks \u0026 Workflow Builder Plugin","id":"CVE-2024-13838","kev_date_added":null,"published":"2025-03-12"},{"cvss_score":5.4,"headline":"Uncanny Automator \u003c= 6.4.0.2 - Missing Authorization to Authenticated (Subscriber+) Plugin Settings Update","id":"CVE-2025-4520","kev_date_added":null,"published":"2025-05-14"}],"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":"partial"},"state":"PUBLISHED","updated":"2026-04-28","vendors":["Uncanny Owl"]},"summary":"An attacker can trick a logged-in admin into resetting license settings in the Uncanny Automator Pro WordPress plugin via CSRF.","url":"https://insights.sbomify.com/CVE-2024-37118/"}