{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2025-6068 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-6068 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-6068 is a medium-severity cross-site scripting vulnerability in fooplugins Gallery by FooGallery, published on 11 Jul 2025. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-6068 and fix it if it is affected.\n\nWhat it is: CVE-2025-6068 is a medium-severity cross-site scripting vulnerability in fooplugins Gallery by FooGallery, published on 11 Jul 2025. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2025-6068 in the wild and no public exploit code.\n\nAffected product: fooplugins Gallery by FooGallery. 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-6068/ (Markdown: https://insights.sbomify.com/CVE-2025-6068/index.md)","id":"CVE-2025-6068","markdown":"https://insights.sbomify.com/CVE-2025-6068/index.md","name":"CVE-2025-6068","record":{"aliases":["GHSA-9p55-rmhm-pj6f"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress plugin","requires_auth":"low_privilege","summary":"Authenticated contributors can inject arbitrary scripts via gallery captions, leading to code execution when users view the page.","user_interaction":"not_required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Wordfence","cpe":[{"product":"foogallery","vendor":"fooplugins"}],"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 FooGallery – Responsive Photo Gallery, Image Viewer, Justified, Masonry \u0026 Carousel plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the `data-caption-title` \u0026 `data-caption-description` HTML attributes in all versions up to, and including, 2.4.31 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with Contributor-level access 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":"Cross-site scripting in Gallery by FooGallery","id":"CVE-2025-6068","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xss","year":"2025"},"n_packages":0,"n_references":3,"next":{"headline":"HTMLParser quadratic complexity when processing malformed inputs","id":"CVE-2025-6069"},"packages":[],"prev":{"headline":"Cross-site scripting in Easy Social Feed – Social Photos Gallery and Post Feed for WordPress","id":"CVE-2025-6067"},"products":["Gallery by FooGallery"],"published":"2025-07-11","related":[{"cvss_score":7.7,"headline":"Best WordPress Gallery Plugin – FooGallery \u003c= 2.4.16 - Authenticated (Contributor+) Directory Traversal","id":"CVE-2023-6947","kev_date_added":null,"published":"2024-12-10"},{"cvss_score":7.1,"headline":"WordPress FooGallery Plugin \u003c= 2.2.44 is vulnerable to Cross Site Scripting (XSS)","id":"CVE-2023-44244","kev_date_added":null,"published":"2023-10-02"},{"cvss_score":7.1,"headline":"WordPress FooGallery Plugin \u003c= 2.2.35 is vulnerable to Cross Site Scripting (XSS)","id":"CVE-2023-29439","kev_date_added":null,"published":"2023-05-16"},{"cvss_score":6.4,"headline":"Cross-site scripting in Gallery by FooGallery","id":"CVE-2024-12119","kev_date_added":null,"published":"2025-03-08"},{"cvss_score":6.4,"headline":"FooGallery \u003c= 2.4.15 - Authenticated (Contributor+) Stored Cross-Site Scripting via Gallery Custom URL","id":"CVE-2024-2122","kev_date_added":null,"published":"2024-06-14"},{"cvss_score":6.4,"headline":"FooGallery \u003c= 2.4.14 - Authenticated (Author+) Stored Cross-Site Scripting","id":"CVE-2024-2081","kev_date_added":null,"published":"2024-04-09"}],"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":["fooplugins"]},"summary":"Authenticated contributors can inject arbitrary scripts via gallery captions, leading to code execution when users view the page.","url":"https://insights.sbomify.com/CVE-2025-6068/"}