{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2023-2285 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2023-2285 yet. Limit exposure of the affected software until one is available.","what":"CVE-2023-2285 is a medium-severity vulnerability in wpwhitesecurity WP Activity Log Premium, published on 9 Jun 2023. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2023-2285 and fix it if it is affected.\n\nWhat it is: CVE-2023-2285 is a medium-severity vulnerability in wpwhitesecurity WP Activity Log Premium, published on 9 Jun 2023. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2023-2285 in the wild and no public exploit code.\n\nAffected product: wpwhitesecurity WP Activity Log Premium. 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-2285/ (Markdown: https://insights.sbomify.com/CVE-2023-2285/index.md)","id":"CVE-2023-2285","markdown":"https://insights.sbomify.com/CVE-2023-2285/index.md","name":"CVE-2023-2285","record":{"aliases":["GHSA-446v-mrg6-7hw8"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress plugin","requires_auth":"low_privilege","summary":"Unauthenticated attackers can trick administrators into modifying plugin settings via a forged request due to missing nonce validation.","user_interaction":"not_required","vuln_class":"csrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Wordfence","cpe":[{"product":"wp_activity_log","vendor":"wpwhitesecurity"}],"cvss":{"score":4.3,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-352","name":"Cross-Site Request Forgery"}],"description":"The WP Activity Log Premium plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to, and including, 4.5.0. This is due to missing or incorrect nonce validation on the ajax_switch_db function. This makes it possible for unauthenticated attackers to make changes to the plugin's settings 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":"WP Activity Log Premium \u003c= 4.5.0 - Cross-Site Request Forgery via ajax_switch_db","id":"CVE-2023-2285","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"csrf","year":"2023"},"n_packages":0,"n_references":2,"next":{"headline":"WP Activity Log \u003c= 4.5.0 - Cross-Site Request Forgery via ajax_run_cleanup","id":"CVE-2023-2286"},"packages":[],"prev":{"headline":"WP Activity Log Premium \u003c= 4.5.0 - Missing Authorization via ajax_switch_db","id":"CVE-2023-2284"},"products":["WP Activity Log Premium"],"published":"2023-06-09","related":[{"cvss_score":7.3,"headline":"WP Activity Log \u003c= 4.0.1 - Missing Authorization","id":"CVE-2020-36716","kev_date_added":null,"published":"2023-06-07"},{"cvss_score":4.3,"headline":"WP Activity Log \u003c= 4.5.0 - Missing Capabilities Check to User Enumeration","id":"CVE-2023-2261","kev_date_added":null,"published":"2023-06-09"},{"cvss_score":4.3,"headline":"WP Activity Log Premium \u003c= 4.5.0 - Missing Authorization via ajax_switch_db","id":"CVE-2023-2284","kev_date_added":null,"published":"2023-06-09"},{"cvss_score":4.3,"headline":"WP Activity Log \u003c= 4.5.0 - Cross-Site Request Forgery via ajax_run_cleanup","id":"CVE-2023-2286","kev_date_added":null,"published":"2023-06-09"}],"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-08","vendors":["wpwhitesecurity"]},"summary":"Unauthenticated attackers can trick administrators into modifying plugin settings via a forged request due to missing nonce validation.","url":"https://insights.sbomify.com/CVE-2023-2285/"}