{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2023-41695 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2023-41695 yet. Limit exposure of the affected software until one is available.","what":"CVE-2023-41695 is a low-severity missing authorization vulnerability in Adnan Analytify, published on 13 Dec 2024. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2023-41695 and fix it if it is affected.\n\nWhat it is: CVE-2023-41695 is a low-severity missing authorization vulnerability in Adnan Analytify, published on 13 Dec 2024. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2023-41695 in the wild and no public exploit code.\n\nAffected product: Adnan Analytify. 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-2023-41695/ (Markdown: https://insights.sbomify.com/CVE-2023-41695/index.md)","id":"CVE-2023-41695","markdown":"https://insights.sbomify.com/CVE-2023-41695/index.md","name":"CVE-2023-41695","record":{"aliases":["GHSA-c37r-7mg5-gpf7"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress plugin","requires_auth":"low_privilege","summary":"Attackers can bypass access controls in the Analytify WordPress plugin to perform unauthorized actions due to missing authorization checks.","user_interaction":"required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Patchstack","cpe":[{"product":"analytify_-_google_analytics_dashboard","vendor":"analytify"}],"cvss":{"score":3.5,"severity":"low","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:N/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-862","name":"Missing Authorization"}],"description":"Missing Authorization vulnerability in Adnan Analytify wp-analytify allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Analytify: from n/a through \u003c= 5.1.0.","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= 5.1.0 - Broken Access Control vulnerability","id":"CVE-2023-41695","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"missing_authorization","year":"2023"},"n_packages":0,"n_references":1,"next":{"headline":"This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.","id":"CVE-2023-41696"},"packages":[],"prev":{"headline":"WordPress Realbig Plugin \u003c= 1.0.3 is vulnerable to Cross Site Request Forgery (CSRF)","id":"CVE-2023-41694"},"products":["Analytify"],"published":"2024-12-13","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-29","vendors":["Adnan"]},"summary":"Attackers can bypass access controls in the Analytify WordPress plugin to perform unauthorized actions due to missing authorization checks.","url":"https://insights.sbomify.com/CVE-2023-41695/"}