{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-28707 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2020-28707 yet. Limit exposure of the affected software until one is available.","what":"CVE-2020-28707 is a medium-severity cross-site scripting vulnerability in n/a, published on 19 Jan 2021. 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-28707 and fix it if it is affected.\n\nWhat it is: CVE-2020-28707 is a medium-severity cross-site scripting vulnerability in n/a, published on 19 Jan 2021. 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-28707 in the wild and no public exploit code.\n\nAffected product: n/a. 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-28707/ (Markdown: https://insights.sbomify.com/CVE-2020-28707/index.md)","id":"CVE-2020-28707","markdown":"https://insights.sbomify.com/CVE-2020-28707/index.md","name":"CVE-2020-28707","record":{"aliases":["GHSA-8rwm-vgc4-5hgx"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress plugin","requires_auth":"none","summary":"Cross-site scripting vulnerability in Stockdio Historical Chart plugin allows attackers to execute arbitrary JavaScript via unvalidated postMessage events.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"stockdio_historical_chart","vendor":"stockdio"}],"cvss":{"score":6.1,"severity":"medium","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/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 Stockdio Historical Chart plugin before 2.8.1 for WordPress is affected by Cross Site Scripting (XSS) via stockdio_chart_historical-wp.js in wp-content/plugins/stockdio-historical-chart/assets/ because the origin of a postMessage() event is not validated. The stockdio_eventer function listens for any postMessage event. After a message event is sent to the application, this function sets the \"e\" variable as the event and checks that the types of the data and data.method are not undefined (empty) before proceeding to eval the data.method received from the postMessage. However, on a different website. JavaScript code can call window.open for the vulnerable WordPress instance and do a postMessage(msg,'*') for that object.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":"2026-09-28","github_poc":1,"max_poc_stars":0,"metasploit":0,"nuclei":0,"refs":[{"date":"2026-09-28T15:20:45Z","kind":"github_poc","ref":"https://github.com/sifatnotes/Learn-SecByte-Venus-Rips-Recon-PHP-CVE-CTF-Labs","stars":0,"title":"Hands-on Learn SecByte CTF labs covering Venus reconnaissance, service discovery, cookies, PHP investigation, secrets, root-focused challenges, and CVE-2020-28707 Stockdio Historical Chart XSS."}],"tier":"poc_unverified"},"has_fix":null,"headline":"Cross-site scripting in n/a","id":"CVE-2020-28707","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xss","year":"2020"},"n_packages":0,"n_references":2,"next":{"headline":"Missing authorization in n/a","id":"CVE-2020-28713"},"packages":[],"prev":{"headline":"Cross-site request forgery in n/a","id":"CVE-2020-28705"},"products":["n/a"],"published":"2021-01-19","related":[{"cvss_score":6.4,"headline":"Stockdio Historical Chart \u003c= 2.8.18 - Authenticated (Contributor+) Stored Cross-Site Scripting","id":"CVE-2024-13349","kev_date_added":null,"published":"2025-01-30"}],"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)"},{"class":"open","licence":"CC0","name":"PoC-in-GitHub"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-07-09","vendors":["n/a"]},"summary":"Cross-site scripting vulnerability in Stockdio Historical Chart plugin allows attackers to execute arbitrary JavaScript via unvalidated postMessage events.","url":"https://insights.sbomify.com/CVE-2020-28707/"}