{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2022-38137 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2022-38137 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-38137 is a medium-severity vulnerability in Analytify (WordPress plugin), published on 8 Nov 2022. 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-2022-38137 and fix it if it is affected.\n\nWhat it is: CVE-2022-38137 is a medium-severity vulnerability in Analytify (WordPress plugin), published on 8 Nov 2022. 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-2022-38137 in the wild and no public exploit code.\n\nAffected product: Analytify (WordPress plugin). 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-38137/ (Markdown: https://insights.sbomify.com/CVE-2022-38137/index.md)","id":"CVE-2022-38137","markdown":"https://insights.sbomify.com/CVE-2022-38137/index.md","name":"CVE-2022-38137","record":{"aliases":["GHSA-7257-7355-6cq2"],"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":"An attacker can trick authenticated users into performing unwanted actions in the Analytify WordPress plugin via CSRF.","user_interaction":"required","vuln_class":"csrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Patchstack","cpe":[{"product":"analytify_-_google_analytics_dashboard","vendor":"analytify"}],"cvss":{"score":4.3,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-352","name":"Cross-Site Request Forgery"}],"description":"Cross-Site Request Forgery (CSRF) vulnerability in Analytify plugin \u003c= 4.2.2 on WordPress.","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":"WordPress Analytify plugin \u003c= 4.2.2 - Cross-Site Request Forgery (CSRF) vulnerability","id":"CVE-2022-38137","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"csrf","year":"2022"},"n_packages":0,"n_references":2,"next":{"headline":"Null dereference in Library: IEC 60870-6 (ICCP/Tase.2)","id":"CVE-2022-38138"},"packages":[],"prev":{"headline":"Path traversal in Intel(R) oneAPI DPC++/C++ Compiler for Windows and Intel® Fortran Compiler for Windows before version 2022.2.1 for some Intel(R) oneAPI Toolkits","id":"CVE-2022-38136"},"products":["Analytify (WordPress plugin)"],"published":"2022-11-08","related":[{"cvss_score":6.5,"headline":"WordPress Analytify - Google Analytics Dashboard plugin \u003c= 4.2.3 - Privilege Escalation vulnerability","id":"CVE-2022-45830","kev_date_added":null,"published":"2025-01-02"},{"cvss_score":6.5,"headline":"WordPress Analytify plugin \u003c= 5.4.3 - Broken Access Control vulnerability","id":"CVE-2024-53814","kev_date_added":null,"published":"2024-12-09"},{"cvss_score":5.4,"headline":"WordPress Analytify plugin \u003c= 5.2.3 - Cross Site Request Forgery (CSRF) vulnerability","id":"CVE-2024-35689","kev_date_added":null,"published":"2024-06-08"},{"cvss_score":5.4,"headline":"Analytify – Google Analytics Dashboard For WordPress (GA4 analytics made easy) \u003c= 5.2.3 - Missing Authorization","id":"CVE-2024-1809","kev_date_added":null,"published":"2024-05-02"},{"cvss_score":5.3,"headline":"Analytify \u003c= 5.2.1 - Missing Authorization to Unauthenticated Google Analytics Tracking ID Modification","id":"CVE-2024-1584","kev_date_added":null,"published":"2024-05-02"},{"cvss_score":4.3,"headline":"WordPress Analytify plugin \u003c= 5.5.1 - Settings Change vulnerability","id":"CVE-2025-30897","kev_date_added":null,"published":"2025-03-27"},{"cvss_score":4.3,"headline":"WordPress Analytify plugin \u003c= 5.5.0 - Broken Access Control vulnerability","id":"CVE-2025-26773","kev_date_added":null,"published":"2025-02-17"}],"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":["Analytify"]},"summary":"An attacker can trick authenticated users into performing unwanted actions in the Analytify WordPress plugin via CSRF.","url":"https://insights.sbomify.com/CVE-2022-38137/"}