{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-3261 exists.","fix":"No fix has been published for CVE-2024-3261 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-3261 is a medium-severity cross-site scripting vulnerability in Unknown Strong Testimonials, published on 24 Apr 2024. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2024-3261 and fix it if it is affected.\n\nWhat it is: CVE-2024-3261 is a medium-severity cross-site scripting vulnerability in Unknown Strong Testimonials, published on 24 Apr 2024. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-3261 exists.\n\nAffected product: Unknown Strong Testimonials. 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-2024-3261/ (Markdown: https://insights.sbomify.com/CVE-2024-3261/index.md)","id":"CVE-2024-3261","markdown":"https://insights.sbomify.com/CVE-2024-3261/index.md","name":"CVE-2024-3261","record":{"aliases":["GHSA-fcw6-ccq2-f46p"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":true,"product_category":"WordPress plugin","requires_auth":"high_privilege","summary":"Contributors can inject malicious scripts via testimonial fields, leading to stored XSS attacks when specific views are rendered.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"WPScan","cpe":[{"product":"strong_testimonials","vendor":"wpchill"}],"cvss":{"score":4.8,"severity":"medium","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:H/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 Strong Testimonials WordPress plugin before 3.1.12 does not validate and escape some of its Testimonial fields before outputting them back in a page/post, which could allow users with the contributor role and above to perform Stored Cross-Site Scripting attacks. The attack requires a specific view to be performed","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":null,"headline":"Strong Testimonials \u003c 3.1.12 - Contributor+ Stored XSS","id":"CVE-2024-3261","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xss","year":"2024"},"n_packages":0,"n_references":1,"next":{"headline":"Information exposure vulnerability in Request Tracker (RT)","id":"CVE-2024-3262"},"packages":[],"prev":{"headline":"This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.","id":"CVE-2024-3260"},"products":["Strong Testimonials"],"published":"2024-04-24","related":[{"cvss_score":6.5,"headline":"WordPress Strong Testimonials Plugin \u003c= 3.0.2 is vulnerable to Cross Site Scripting (XSS)","id":"CVE-2023-26013","kev_date_added":null,"published":"2023-06-16"},{"cvss_score":6.1,"headline":"Cross-site scripting in n/a","id":"CVE-2020-8549","kev_date_added":null,"published":"2020-02-03"},{"cvss_score":4.3,"headline":"WordPress Strong Testimonials plugin \u003c= 3.1.16 - Broken Access Control vulnerability","id":"CVE-2024-47362","kev_date_added":null,"published":"2024-11-01"},{"cvss_score":4.3,"headline":"Strong Testimonials \u003c= 3.1.12 - Authenticated(Contributor+) Improper Authorization to Views Modification","id":"CVE-2023-6491","kev_date_added":null,"published":"2024-06-07"},{"cvss_score":4.3,"headline":"WordPress Strong Testimonials Plugin \u003c= 3.1.10 is vulnerable to Cross Site Request Forgery (CSRF)","id":"CVE-2023-52123","kev_date_added":null,"published":"2024-01-05"}],"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":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2024-08-01","vendors":["Unknown"]},"summary":"Contributors can inject malicious scripts via testimonial fields, leading to stored XSS attacks when specific views are rendered.","url":"https://insights.sbomify.com/CVE-2024-3261/"}