{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2023-36518 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2023-36518 yet. Limit exposure of the affected software until one is available.","what":"CVE-2023-36518 is a medium-severity missing authorization vulnerability in Hugh Lashbrooke Post Hit Counter, published on 13 Dec 2024. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2023-36518 and fix it if it is affected.\n\nWhat it is: CVE-2023-36518 is a medium-severity missing authorization vulnerability in Hugh Lashbrooke Post Hit Counter, published on 13 Dec 2024. 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-36518 in the wild and no public exploit code.\n\nAffected product: Hugh Lashbrooke Post Hit Counter. 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-36518/ (Markdown: https://insights.sbomify.com/CVE-2023-36518/index.md)","id":"CVE-2023-36518","markdown":"https://insights.sbomify.com/CVE-2023-36518/index.md","name":"CVE-2023-36518","record":{"aliases":["GHSA-jf99-j3rv-qp5p"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["data_read","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress plugin","requires_auth":"low_privilege","summary":"Attackers can bypass access controls to read or modify hit counter data in the Post Hit Counter WordPress plugin.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Patchstack","cpe":[],"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-862","name":"Missing Authorization"}],"description":"Missing Authorization vulnerability in Hugh Lashbrooke Post Hit Counter allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Post Hit Counter: from n/a through 1.3.2.","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 Post Hit Counter plugin \u003c= 1.3.2 - Broken Access Control","id":"CVE-2023-36518","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":"WordPress SW Product Bundles plugin \u003c= 2.0.15 - Broken Access Control vulnerability","id":"CVE-2023-36519"},"packages":[],"prev":{"headline":"WordPress WP Abstracts Plugin \u003c= 2.6.2 is vulnerable to Cross Site Request Forgery (CSRF)","id":"CVE-2023-36517"},"products":["Post Hit Counter"],"published":"2024-12-13","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"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":["Hugh Lashbrooke"]},"summary":"Attackers can bypass access controls to read or modify hit counter data in the Post Hit Counter WordPress plugin.","url":"https://insights.sbomify.com/CVE-2023-36518/"}