{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-36761 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2020-36761 yet. Limit exposure of the affected software until one is available.","what":"CVE-2020-36761 is a medium-severity vulnerability in ajay WebberZone Top 10 — Popular Posts, published on 12 Jul 2023. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2020-36761 and fix it if it is affected.\n\nWhat it is: CVE-2020-36761 is a medium-severity vulnerability in ajay WebberZone Top 10 — Popular Posts, published on 12 Jul 2023. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2020-36761 in the wild and no public exploit code.\n\nAffected product: ajay WebberZone Top 10 — Popular Posts. 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-2020-36761/ (Markdown: https://insights.sbomify.com/CVE-2020-36761/index.md)","id":"CVE-2020-36761","markdown":"https://insights.sbomify.com/CVE-2020-36761/index.md","name":"CVE-2020-36761","record":{"aliases":["GHSA-2xcx-834w-fp84"],"analysis":{"component_type":"cms_plugin","fix_type":"patch","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress plugin","requires_auth":"none","summary":"Unauthenticated attackers can trick administrators into exporting top 10 tables via CSRF, exposing data.","user_interaction":"required","vuln_class":"csrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Wordfence","cpe":[{"product":"top_10","vendor":"webberzone"}],"cvss":{"score":4.3,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-352","name":"Cross-Site Request Forgery"}],"description":"The Top 10 plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to, and including, 2.10.4. This is due to missing or incorrect nonce validation on the tptn_export_tables() function. This makes it possible for unauthenticated attackers to generate an export of the top 10 table via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Top 10 \u003c= 2.9.4 - Cross-Site Request Forgery Bypass","id":"CVE-2020-36761","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"csrf","year":"2020"},"n_packages":0,"n_references":9,"next":{"headline":"ONS Digital RAS Collection Instrument comment.yml jobs os command injection","id":"CVE-2020-36762"},"packages":[],"prev":{"headline":"Ocean Extra \u003c=1.6.5 - Cross-Site Request Forgery Bypass","id":"CVE-2020-36760"},"products":["WebberZone Top 10 — Popular Posts"],"published":"2023-07-12","related":[{"cvss_score":4.3,"headline":"WordPress Top 10 – Popular posts plugin for WordPress plugin \u003c= 3.2.3 - Broken Access Control vulnerability","id":"CVE-2023-25993","kev_date_added":null,"published":"2024-12-09"},{"cvss_score":4.3,"headline":"WordPress Top 10 Plugin \u003c= 3.3.2 is vulnerable to Cross Site Request Forgery (CSRF)","id":"CVE-2023-47238","kev_date_added":null,"published":"2023-11-09"}],"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-08","vendors":["ajay"]},"summary":"Unauthenticated attackers can trick administrators into exporting top 10 tables via CSRF, exposing data.","url":"https://insights.sbomify.com/CVE-2020-36761/"}