{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2025-26841 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-26841 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-26841 is a medium-severity cross-site scripting vulnerability in n/a, published on 12 May 2025. 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-2025-26841 and fix it if it is affected.\n\nWhat it is: CVE-2025-26841 is a medium-severity cross-site scripting vulnerability in n/a, published on 12 May 2025. 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-2025-26841 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-2025-26841/ (Markdown: https://insights.sbomify.com/CVE-2025-26841/index.md)","id":"CVE-2025-26841","markdown":"https://insights.sbomify.com/CVE-2025-26841/index.md","name":"CVE-2025-26841","record":{"aliases":["GHSA-g988-pqhg-r7m5"],"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":"An attacker can execute arbitrary code via a file upload in the Everest Forms WordPress plugin.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"everest_forms","vendor":"wpeverest"}],"cvss":{"score":6.1,"severity":"medium","source":"cisa-adp","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":"Cross Site Scripting vulnerability in WPEVEREST Everest Forms before 3.0.9 allows an attacker to execute arbitrary code via a file upload.","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":"Cross-site scripting in n/a","id":"CVE-2025-26841","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xss","year":"2025"},"n_packages":0,"n_references":2,"next":{"headline":"Missing authorization in n/a","id":"CVE-2025-26842"},"packages":[],"prev":{"headline":"Denial of service in Monero","id":"CVE-2025-26819"},"products":["n/a"],"published":"2025-05-12","related":[{"cvss_score":9.8,"headline":"Deserialization in Everest Forms – Contact Form, Payment Form, Quiz, Survey \u0026 Custom Form Builder","id":"CVE-2025-3439","kev_date_added":null,"published":"2025-04-11"},{"cvss_score":9.8,"headline":"Everest Forms \u003c= 3.0.9.4 - Unauthenticated Arbitrary File Upload, Read, and Deletion","id":"CVE-2025-1128","kev_date_added":null,"published":"2025-02-25"},{"cvss_score":9.8,"headline":"SQL injection in n/a","id":"CVE-2019-13575","kev_date_added":null,"published":"2019-07-18"},{"cvss_score":7.5,"headline":"Everest Forms (Pro) \u003c= 1.9.4 - Unauthenticated Path Traversal to Arbitrary File Deletion","id":"CVE-2025-5927","kev_date_added":null,"published":"2025-06-25"},{"cvss_score":7.2,"headline":"Everest Forms \u003c= 2.0.7 - Unauthenticated Server-Side Request Forgery via font_url","id":"CVE-2024-1812","kev_date_added":null,"published":"2024-04-09"},{"cvss_score":6.1,"headline":"Everest Forms \u003c= 3.1.1 - Reflected Cross-Site Scripting","id":"CVE-2025-3421","kev_date_added":null,"published":"2025-04-11"}],"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":"2025-05-12","vendors":["n/a"]},"summary":"An attacker can execute arbitrary code via a file upload in the Everest Forms WordPress plugin.","url":"https://insights.sbomify.com/CVE-2025-26841/"}