{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2021-25117 exists.","fix":"No fix has been published for CVE-2021-25117 yet. Limit exposure of the affected software until one is available.","what":"CVE-2021-25117 is a medium-severity cross-site scripting vulnerability in Unknown WP-PostRatings, published on 16 Jan 2024. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2021-25117 and fix it if it is affected.\n\nWhat it is: CVE-2021-25117 is a medium-severity cross-site scripting vulnerability in Unknown WP-PostRatings, published on 16 Jan 2024. An attacker needs administrator access to exploit it, 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-2021-25117 exists.\n\nAffected product: Unknown WP-PostRatings. 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-2021-25117/ (Markdown: https://insights.sbomify.com/CVE-2021-25117/index.md)","id":"CVE-2021-25117","markdown":"https://insights.sbomify.com/CVE-2021-25117/index.md","name":"CVE-2021-25117","record":{"aliases":["GHSA-5c46-pxg6-m63r"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":true,"product_category":"WordPress plugin","requires_auth":"high_privilege","summary":"Administrators can inject malicious scripts via the postratings_image parameter when unfiltered_html is disabled, leading to stored XSS.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"WPScan","cpe":[{"product":"wp-postratings","vendor":"lesterchan"}],"cvss":{"score":4.8,"severity":"medium","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:L/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-352","name":"Cross-Site Request Forgery"}],"description":"The WP-PostRatings WordPress plugin before 1.86.1 does not sanitise the postratings_image parameter from its options page (wp-admin/admin.php?page=wp-postratings/postratings-options.php). Even though the page is only accessible to administrators, and protected against CSRF attacks, the issue is still exploitable when the unfiltered_html capability is disabled.","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":"WP Postratings \u003c 1.86.1 - Admin+ Stored Cross-Site Scripting","id":"CVE-2021-25117","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xss","year":"2021"},"n_packages":0,"n_references":1,"next":{"headline":"Yoast SEO 16.7-17.2 - Unauthenticated Full Path Disclosure","id":"CVE-2021-25118"},"packages":[],"prev":{"headline":"Enqueue Anything \u003c= 1.0.1 - Subscriber+ Arbitrary Asset/Post Deletion","id":"CVE-2021-25116"},"products":["WP-PostRatings"],"published":"2024-01-16","related":[{"cvss_score":6.5,"headline":"WordPress WP-PostRatings plugin \u003c= 1.91.1 - Cross Site Scripting (XSS) vulnerability","id":"CVE-2024-39659","kev_date_added":null,"published":"2024-08-01"},{"cvss_score":6,"headline":"SQL injection in n/a","id":"CVE-2011-4646","kev_date_added":null,"published":"2011-11-30"},{"cvss_score":5.3,"headline":"WordPress WP-PostRatings plugin \u003c= 1.91 - Rating limit Bypass vulnerability","id":"CVE-2023-40332","kev_date_added":null,"published":"2024-06-04"},{"cvss_score":3.5,"headline":"GamerZ WP-PostRatings wp-postratings.php cross site scripting","id":"CVE-2011-10006","kev_date_added":null,"published":"2024-04-08"}],"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":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-06-17","vendors":["Unknown"]},"summary":"Administrators can inject malicious scripts via the postratings_image parameter when unfiltered_html is disabled, leading to stored XSS.","url":"https://insights.sbomify.com/CVE-2021-25117/"}