{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2023-6947 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2023-6947 yet. Limit exposure of the affected software until one is available.","what":"CVE-2023-6947 is a high-severity path traversal vulnerability in https://fooplugins.com FooGallery Premium, published on 10 Dec 2024. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2023-6947 and fix it if it is affected.\n\nWhat it is: CVE-2023-6947 is a high-severity path traversal vulnerability in https://fooplugins.com FooGallery Premium, published on 10 Dec 2024. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2023-6947 in the wild and no public exploit code.\n\nAffected product: https://fooplugins.com FooGallery Premium. 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-2023-6947/ (Markdown: https://insights.sbomify.com/CVE-2023-6947/index.md)","id":"CVE-2023-6947","markdown":"https://insights.sbomify.com/CVE-2023-6947/index.md","name":"CVE-2023-6947","record":{"aliases":["GHSA-9q34-p9w7-3f57"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress gallery plugin","requires_auth":"low_privilege","summary":"Authenticated contributors can read arbitrary server folders via directory traversal in FooGallery, exposing sensitive information.","user_interaction":"not_required","vuln_class":"path_traversal"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Wordfence","cpe":[{"product":"foogallery","vendor":"fooplugins"}],"cvss":{"score":7.7,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-22","name":"Improper Limitation of a Pathname to a Restricted Directory"},{"id":"CWE-25","name":"Path Traversal: '/../filedir'"}],"description":"The Best WordPress Gallery Plugin – FooGallery plugin for WordPress is vulnerable to Directory Traversal in all versions up to, and including, 2.4.26. This makes it possible for authenticated attackers, with contributor level or higher to read the contents of arbitrary folders on the server, which can contain sensitive information such as folder structure.","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":"Best WordPress Gallery Plugin – FooGallery \u003c= 2.4.16 - Authenticated (Contributor+) Directory Traversal","id":"CVE-2023-6947","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"path_traversal","year":"2023"},"n_packages":0,"n_references":2,"next":{"headline":"Memory corruption in Matrice 300","id":"CVE-2023-6948"},"packages":[],"prev":{"headline":"Autotitle for WordPress \u003c= 1.0.3 - Settings Update to Stored XSS via CSRF","id":"CVE-2023-6946"},"products":["FooGallery Premium"],"published":"2024-12-10","related":[{"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-2025-6068","kev_date_added":null,"published":"2025-07-11"},{"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":["https://fooplugins.com"]},"summary":"Authenticated contributors can read arbitrary server folders via directory traversal in FooGallery, exposing sensitive information.","url":"https://insights.sbomify.com/CVE-2023-6947/"}