{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-4673 exists.","fix":"No fix has been published for CVE-2022-4673 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-4673 is a medium-severity cross-site scripting vulnerability in Unknown Rate my Post, published on 23 Jan 2023. 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-2022-4673 and fix it if it is affected.\n\nWhat it is: CVE-2022-4673 is a medium-severity cross-site scripting vulnerability in Unknown Rate my Post, published on 23 Jan 2023. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-4673 exists.\n\nAffected product: Unknown Rate my Post. 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-4673/ (Markdown: https://insights.sbomify.com/CVE-2022-4673/index.md)","id":"CVE-2022-4673","markdown":"https://insights.sbomify.com/CVE-2022-4673/index.md","name":"CVE-2022-4673","record":{"aliases":["GHSA-6x9q-3f3x-4w22"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress plugin","requires_auth":"low_privilege","summary":"Contributors can inject malicious scripts via shortcode attributes in the Rate my Post plugin, potentially compromising user sessions.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"WPScan","cpe":[{"product":"rate_my_post","vendor":"blazzdev"}],"cvss":{"score":5.4,"severity":"medium","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N","version":"3.1"},"cwes":[],"description":"The Rate my Post WordPress plugin before 3.3.9 does not validate and escape one of its shortcode attributes, which could allow users with a role as low as contributor to perform Stored Cross-Site Scripting attack.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":null,"headline":"Rate my Post – WP Rating System \u003c 3.3.9 - Contributor+ Stored XSS via Shortcode","id":"CVE-2022-4673","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xss","year":"2022"},"n_packages":0,"n_references":1,"next":{"headline":"Ibtana – WordPress Website Builder \u003c 1.1.8.8 - Contributor+ Stored XSS via Shortcode","id":"CVE-2022-4674"},"packages":[],"prev":{"headline":"WordPress Simple Shopping Cart \u003c 4.6.2 - Contributor+ Stored XSS via Shortcode","id":"CVE-2022-4672"},"products":["Rate my Post"],"published":"2023-01-23","related":[{"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":5.3,"headline":"WordPress Rate My Post plugin \u003c= 3.4.4 - Insecure Direct Object References (IDOR) vulnerability","id":"CVE-2024-32823","kev_date_added":null,"published":"2024-04-24"},{"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":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-04-02","vendors":["Unknown"]},"summary":"Contributors can inject malicious scripts via shortcode attributes in the Rate my Post plugin, potentially compromising user sessions.","url":"https://insights.sbomify.com/CVE-2022-4673/"}