{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2021-4408 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2021-4408 yet. Limit exposure of the affected software until one is available.","what":"CVE-2021-4408 is a medium-severity vulnerability in designwall DW Question \u0026 Answer, 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-2021-4408 and fix it if it is affected.\n\nWhat it is: CVE-2021-4408 is a medium-severity vulnerability in designwall DW Question \u0026 Answer, 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-2021-4408 in the wild and no public exploit code.\n\nAffected product: designwall DW Question \u0026 Answer. 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-4408/ (Markdown: https://insights.sbomify.com/CVE-2021-4408/index.md)","id":"CVE-2021-4408","markdown":"https://insights.sbomify.com/CVE-2021-4408/index.md","name":"CVE-2021-4408","record":{"aliases":["GHSA-99wh-w7pr-c2vh"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress plugin","requires_auth":"none","summary":"Unauthenticated attackers can modify question answers by tricking administrators into clicking a link due to missing nonce validation.","user_interaction":"required","vuln_class":"csrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Wordfence","cpe":[{"product":"dw_question_\\\u0026_answer","vendor":"designwall"}],"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 DW Question \u0026 Answer plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to, and including, 1.5.8. This is due to missing or incorrect nonce validation on the update_answer() function. This makes it possible for unauthenticated attackers to update answers to questions 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":null,"headline":"DW Question \u0026 Answer \u003c= 1.5.8 - Cross-Site Request Forgery Bypass","id":"CVE-2021-4408","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"csrf","year":"2021"},"n_packages":0,"n_references":9,"next":{"headline":"WooCommerce Etsy Integration \u003c= 3.3.1 - Cross-Site Request Forgery Bypass","id":"CVE-2021-4409"},"packages":[],"prev":{"headline":"Custom Banners \u003c= 3.2.2 - Cross-Site Request Forgery Bypass","id":"CVE-2021-4407"},"products":["DW Question \u0026 Answer"],"published":"2023-07-12","related":[{"cvss_score":4.3,"headline":"DW Question \u0026 Answer Pro \u003c= 1.3.4 - Arbitrary Comment Edition via IDOR","id":"CVE-2021-24800","kev_date_added":null,"published":"2022-04-25"},{"cvss_score":4.3,"headline":"DW Question \u0026 Answer Pro \u003c= 1.3.4 - Multiple CSRF","id":"CVE-2021-24805","kev_date_added":null,"published":"2022-04-25"}],"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":["designwall"]},"summary":"Unauthenticated attackers can modify question answers by tricking administrators into clicking a link due to missing nonce validation.","url":"https://insights.sbomify.com/CVE-2021-4408/"}