{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2024-3682 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2024-3682 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-3682 is a medium-severity vulnerability in WPStaging WP STAGING Pro WordPress Backup Plugin, published on 26 Apr 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-3682 and fix it if it is affected.\n\nWhat it is: CVE-2024-3682 is a medium-severity vulnerability in WPStaging WP STAGING Pro WordPress Backup Plugin, published on 26 Apr 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-3682 in the wild and no public exploit code.\n\nAffected product: WPStaging WP STAGING Pro WordPress Backup Plugin. 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-3682/ (Markdown: https://insights.sbomify.com/CVE-2024-3682/index.md)","id":"CVE-2024-3682","markdown":"https://insights.sbomify.com/CVE-2024-3682/index.md","name":"CVE-2024-3682","record":{"aliases":["GHSA-q66w-qfxv-vpx3"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":true,"product_category":"WordPress staging plugin","requires_auth":"none","summary":"Unauthenticated attackers can extract sensitive system data and license keys from log files if specific admin settings are enabled.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Wordfence","cpe":[],"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-200","name":"Exposure of Sensitive Information to an Unauthorized Actor"}],"description":"The WP STAGING and WP STAGING Pro plugins for WordPress are vulnerable to Sensitive Information Exposure in versions up to, and including, 3.4.3, and versions up to, and including, 5.4.3, respectively, via the ajaxSendReport function. This makes it possible for unauthenticated attackers to extract sensitive data from a log file, including system information and (in the Pro version) license keys. Successful exploitation requires an administrator to have used the 'Contact Us' functionality along with the \"Enable this option to automatically submit the log files.\" option.","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":"WP STAGING \u003c= 3.4.3 and WP STAGING Pro \u003c= 5.4.3 - Sensitive Information Exposure via Log File","id":"CVE-2024-3682","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2024"},"n_packages":0,"n_references":4,"next":{"headline":"Server-side request forgery in Enterprise Server","id":"CVE-2024-3684"},"packages":[],"prev":{"headline":"Interactive World Maps \u003c= 2.4.14 - Reflected Cross-Site Scripting","id":"CVE-2024-3681"},"products":["WP STAGING Pro WordPress Backup Plugin","WP STAGING – WordPress Backup, Restore \u0026 Migration"],"published":"2024-04-26","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"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":["WPStaging","renehermi"]},"summary":"Unauthenticated attackers can extract sensitive system data and license keys from log files if specific admin settings are enabled.","url":"https://insights.sbomify.com/CVE-2024-3682/"}