{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-36711 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2020-36711 yet. Limit exposure of the affected software until one is available.","what":"CVE-2020-36711 is a medium-severity cross-site scripting vulnerability in ThemeFusion Avada | Website Builder For WordPress \u0026 WooCommerce, published on 7 Jun 2023. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2020-36711 and fix it if it is affected.\n\nWhat it is: CVE-2020-36711 is a medium-severity cross-site scripting vulnerability in ThemeFusion Avada | Website Builder For WordPress \u0026 WooCommerce, published on 7 Jun 2023. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2020-36711 in the wild and no public exploit code.\n\nAffected product: ThemeFusion Avada | Website Builder For WordPress \u0026 WooCommerce. 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-36711/ (Markdown: https://insights.sbomify.com/CVE-2020-36711/index.md)","id":"CVE-2020-36711","markdown":"https://insights.sbomify.com/CVE-2020-36711/index.md","name":"CVE-2020-36711","record":{"aliases":["GHSA-pf5j-34m8-jf87"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress theme","requires_auth":"low_privilege","summary":"Authenticated contributors can inject arbitrary scripts into pages via the update_layout function, leading to stored XSS execution for other users.","user_interaction":"not_required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Wordfence","cpe":[{"product":"avada","vendor":"theme-fusion"}],"cvss":{"score":6.4,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/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 Avada theme for WordPress is vulnerable to Stored Cross-Site Scripting via the update_layout function in versions up to, and including, 6.2.3 due to insufficient input sanitization and output escaping. This makes it possible for contributor-level attackers, and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.","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":"Avada \u003c= 6.2.2 - Authenticated (Contributor+) Cross-Site Scripting","id":"CVE-2020-36711","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xss","year":"2020"},"n_packages":0,"n_references":3,"next":{"headline":"Kali Forms \u003c= 2.1.1 - Unauthenticated Arbitrary Post Deletion","id":"CVE-2020-36712"},"packages":[],"prev":{"headline":"WPS Hide Login \u003c= 1.5.4.2 - Hidden Login Page Location Disclosure","id":"CVE-2020-36710"},"products":["Avada | Website Builder For WordPress \u0026 WooCommerce"],"published":"2023-06-07","related":[{"cvss_score":9.1,"headline":"WordPress Avada theme \u003c= 7.11.1 - Auth. Unrestricted Zip Extraction vulnerability","id":"CVE-2023-39312","kev_date_added":null,"published":"2024-06-19"},{"cvss_score":8.8,"headline":"Avada | Website Builder For WordPress \u0026 WooCommerce \u003c= 7.11.4 - Authenticated (Contributor+) Arbitrary File Upload","id":"CVE-2024-1468","kev_date_added":null,"published":"2024-02-29"},{"cvss_score":8.8,"headline":"WordPress Avada premium theme \u003c= 7.8.1 - Cross-Site Request Forgery (CSRF) vulnerability","id":"CVE-2022-41996","kev_date_added":null,"published":"2022-10-27"},{"cvss_score":8.8,"headline":"Cross-site request forgery in n/a","id":"CVE-2017-18607","kev_date_added":null,"published":"2019-09-10"},{"cvss_score":8.5,"headline":"WordPress Avada theme \u003c= 7.11.1 - Authenticated Arbitrary File Upload vulnerability","id":"CVE-2023-39307","kev_date_added":null,"published":"2024-03-26"},{"cvss_score":7.7,"headline":"WordPress Avada theme \u003c= 7.11.1 - Authenticated Server Side Request Forgery (SSRF) vulnerability","id":"CVE-2023-39313","kev_date_added":null,"published":"2024-03-28"},{"cvss_score":7.3,"headline":"Avada Theme \u003c= 7.11.13 - Unauthenticated Arbitrary Shortcode Execution","id":"CVE-2024-13346","kev_date_added":null,"published":"2025-02-13"}],"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":["ThemeFusion"]},"summary":"Authenticated contributors can inject arbitrary scripts into pages via the update_layout function, leading to stored XSS execution for other users.","url":"https://insights.sbomify.com/CVE-2020-36711/"}