{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2024-6687 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2024-6687 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-6687 is a medium-severity vulnerability in limpinho CTT Expresso para WooCommerce, published on 1 Aug 2024. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2024-6687 and fix it if it is affected.\n\nWhat it is: CVE-2024-6687 is a medium-severity vulnerability in limpinho CTT Expresso para WooCommerce, published on 1 Aug 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2024-6687 in the wild and no public exploit code.\n\nAffected product: limpinho CTT Expresso para WooCommerce. 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-6687/ (Markdown: https://insights.sbomify.com/CVE-2024-6687/index.md)","id":"CVE-2024-6687","markdown":"https://insights.sbomify.com/CVE-2024-6687/index.md","name":"CVE-2024-6687","record":{"aliases":["GHSA-73q4-cgh7-2r7w"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress plugin","requires_auth":"none","summary":"Attackers can access sensitive personal data from unprotected PDF and log files in the plugin's upload directory.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Wordfence","cpe":[{"product":"ctt_expresso_para_woocommerce","vendor":"thisfunctional"}],"cvss":{"score":5.3,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-532","name":"Insertion of Sensitive Information into Log File"},{"id":"CWE-200","name":"Exposure of Sensitive Information to an Unauthorized Actor"}],"description":"The CTT Expresso para WooCommerce plugin for WordPress is vulnerable to sensitive information exposure in all versions up to and including 3.2.12 via the /wp-content/uploads/cepw directory. The generated .pdf and log files are publicly accessible and contain sensitive information such as sender and receiver names, phone numbers, physical addresses, and email addresses","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":"CTT Expresso para WooCommerce \u003c= 3.2.12 - Information Exposure via Unprotected Directory","id":"CVE-2024-6687","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2024"},"n_packages":0,"n_references":2,"next":{"headline":"Oxygen Builder \u003c= 4.8.3 - Missing Authorization to Authenticated (Subscriber+) Stylesheet Update","id":"CVE-2024-6688"},"packages":[],"prev":{"headline":"Authorization Bypass Through User-Controlled Key in GitLab","id":"CVE-2024-6685"},"products":["CTT Expresso para WooCommerce"],"published":"2024-08-01","related":[{"cvss_score":5.9,"headline":"WordPress CTT Expresso para WooCommerce Plugin \u003c= 3.2.11 is vulnerable to Cross Site Scripting (XSS)","id":"CVE-2022-47589","kev_date_added":null,"published":"2023-03-23"},{"cvss_score":4.8,"headline":"CTT Expresso para WooCommerce \u003c 3.2.13 - Admin+ Stored XSS","id":"CVE-2024-6478","kev_date_added":null,"published":"2025-05-15"}],"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":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-04-08","vendors":["limpinho"]},"summary":"Attackers can access sensitive personal data from unprotected PDF and log files in the plugin's upload directory.","url":"https://insights.sbomify.com/CVE-2024-6687/"}