{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2024-32823 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2024-32823 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-32823 is a medium-severity missing authorization vulnerability in FeedbackWP Rate my Post – WP Rating System, published on 24 Apr 2024. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2024-32823 and fix it if it is affected.\n\nWhat it is: CVE-2024-32823 is a medium-severity missing authorization vulnerability in FeedbackWP Rate my Post – WP Rating System, published on 24 Apr 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2024-32823 in the wild and no public exploit code.\n\nAffected product: FeedbackWP Rate my Post – WP Rating System. 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-32823/ (Markdown: https://insights.sbomify.com/CVE-2024-32823/index.md)","id":"CVE-2024-32823","markdown":"https://insights.sbomify.com/CVE-2024-32823/index.md","name":"CVE-2024-32823","record":{"aliases":["GHSA-8fp3-p8fq-633j"],"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":"none","summary":"Attackers can bypass authorization to access or modify data via user-controlled keys in the Rate My Post WordPress plugin.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Patchstack","cpe":[{"product":"rate_my_post","vendor":"blazzdev"}],"cvss":{"score":5.3,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-639","name":"Authorization Bypass Through User-Controlled Key"}],"description":"Authorization Bypass Through User-Controlled Key vulnerability in FeedbackWP Rate my Post – WP Rating System.This issue affects Rate my Post – WP Rating System: from n/a through 3.4.4.","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 Rate My Post plugin \u003c= 3.4.4 - Insecure Direct Object References (IDOR) vulnerability","id":"CVE-2024-32823","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"missing_authorization","year":"2024"},"n_packages":0,"n_references":1,"next":{"headline":"WordPress Evergreen Content Poster plugin \u003c= 1.4.2 - Broken Access Control vulnerability","id":"CVE-2024-32824"},"packages":[],"prev":{"headline":"WordPress Reviews Plus plugin \u003c= 1.3.4 - Broken Access Control vulnerability","id":"CVE-2024-32822"},"products":["Rate my Post – WP Rating System"],"published":"2024-04-24","related":[{"cvss_score":5.4,"headline":"Rate my Post – WP Rating System \u003c 3.3.9 - Contributor+ Stored XSS via Shortcode","id":"CVE-2022-4673","kev_date_added":null,"published":"2023-01-23"},{"cvss_score":5.3,"headline":"WordPress Rate my Post – WP Rating System plugin \u003c= 3.4.2 - Broken Access Control vulnerability","id":"CVE-2023-51667","kev_date_added":null,"published":"2024-06-04"},{"cvss_score":4.3,"headline":"WordPress Rate my Post – WP Rating System Plugin \u003c= 3.4.1 is vulnerable to Insecure Direct Object References (IDOR)","id":"CVE-2023-49765","kev_date_added":null,"published":"2023-12-21"}],"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":["FeedbackWP"]},"summary":"Attackers can bypass authorization to access or modify data via user-controlled keys in the Rate My Post WordPress plugin.","url":"https://insights.sbomify.com/CVE-2024-32823/"}