{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2021-24509 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2021-24509 yet. Limit exposure of the affected software until one is available.","what":"CVE-2021-24509 is a medium-severity cross-site scripting vulnerability in Unknown Page View Count, published on 9 Aug 2021. 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-2021-24509 and fix it if it is affected.\n\nWhat it is: CVE-2021-24509 is a medium-severity cross-site scripting vulnerability in Unknown Page View Count, published on 9 Aug 2021. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2021-24509 in the wild and no public exploit code.\n\nAffected product: Unknown Page View Count. 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-24509/ (Markdown: https://insights.sbomify.com/CVE-2021-24509/index.md)","id":"CVE-2021-24509","markdown":"https://insights.sbomify.com/CVE-2021-24509/index.md","name":"CVE-2021-24509","record":{"aliases":["GHSA-qjp7-r5pf-4fvh"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["code_execution","account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress plugin","requires_auth":"low_privilege","summary":"Contributors can inject malicious scripts via the postid parameter in the Page View Count plugin, potentially leading to code execution or account takeover.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"WPScan","cpe":[{"product":"page_view_count","vendor":"a3rev"}],"cvss":{"score":5.4,"severity":"medium","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-79","name":"Improper Neutralization of Input During Web Page Generation"}],"description":"The Page View Count WordPress plugin before 2.4.9 does not escape the postid parameter of pvc_stats shortcode, allowing users with a role as low as Contributor to perform Stored XSS attacks. A post made by a contributor would still have to be approved by an admin to have the XSS triggered in the frontend, however, higher privilege users, such as editor could exploit this without the need of approval, and even when the blog disallows the unfiltered_html capability.","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":"Page View Counts \u003c 2.4.9 - Contributor+ Stored XSS","id":"CVE-2021-24509","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xss","year":"2021"},"n_packages":0,"n_references":1,"next":{"headline":"MF Gig Calendar \u003c 1.2 - Reflected Cross-Site Scripting (XSS)","id":"CVE-2021-24510"},"packages":[],"prev":{"headline":"Smash Balloon Social Post Feed \u003c 2.19.2 - Unauthenticated Stored XSS","id":"CVE-2021-24508"},"products":["Page View Count"],"published":"2021-08-09","related":[{"cvss_score":9.8,"headline":"Page Views Count \u003c 2.4.15 - Unauthenticated SQL Injection","id":"CVE-2022-0434","kev_date_added":null,"published":"2022-03-07"},{"cvss_score":8.1,"headline":"Page View Count 2.8.0 - 2.8.4 - Missing Authorization to Authenticated (Subscriber+) Limited Options Update","id":"CVE-2025-2816","kev_date_added":null,"published":"2025-05-01"},{"cvss_score":5.4,"headline":"Page View Count \u003c 2.6.1 - Contributor+ Stored XSS","id":"CVE-2023-0095","kev_date_added":null,"published":"2023-02-06"},{"cvss_score":5.4,"headline":"WordPress Page View Count plugin \u003c= 2.5.5 - Cross-Site Request Forgery (CSRF) vulnerability","id":"CVE-2022-40131","kev_date_added":null,"published":"2022-11-03"}],"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":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-03","vendors":["Unknown"]},"summary":"Contributors can inject malicious scripts via the postid parameter in the Page View Count plugin, potentially leading to code execution or account takeover.","url":"https://insights.sbomify.com/CVE-2021-24509/"}