{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2023-5504 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2023-5504 yet. Limit exposure of the affected software until one is available.","what":"CVE-2023-5504 is a high-severity path traversal vulnerability in wp_media BackWPup – WordPress Backup \u0026 Restore Plugin, published on 11 Jan 2024. An attacker needs administrator access to exploit it, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2023-5504 and fix it if it is affected.\n\nWhat it is: CVE-2023-5504 is a high-severity path traversal vulnerability in wp_media BackWPup – WordPress Backup \u0026 Restore Plugin, published on 11 Jan 2024. An attacker needs administrator access to exploit it, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2023-5504 in the wild and no public exploit code.\n\nAffected product: wp_media BackWPup – WordPress Backup \u0026 Restore 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-2023-5504/ (Markdown: https://insights.sbomify.com/CVE-2023-5504/index.md)","id":"CVE-2023-5504","markdown":"https://insights.sbomify.com/CVE-2023-5504/index.md","name":"CVE-2023-5504","record":{"aliases":["GHSA-mh4j-2c4w-jxfr"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["data_modify","denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress plugin","requires_auth":"high_privilege","summary":"Authenticated administrators can exploit directory traversal to store backups in arbitrary folders, potentially disabling other sites in shared environments.","user_interaction":"not_required","vuln_class":"path_traversal"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Wordfence","cpe":[{"product":"backwpup","vendor":"inpsyde"}],"cvss":{"score":8.7,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:N/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-22","name":"Improper Limitation of a Pathname to a Restricted Directory"}],"description":"The BackWPup plugin for WordPress is vulnerable to Directory Traversal in versions up to, and including, 4.0.1 via the Log File Folder. This allows authenticated attackers to store backups in arbitrary folders on the server provided they can be written to by the server. Additionally, default settings will place an index.php and a .htaccess file into the chosen directory (unless already present) when the first backup job is run that are intended to prevent directory listing and file access. This means that an attacker could set the backup directory to the root of another site in a shared environment and thus disable that site.","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":"BackWPup \u003c= 4.0.1 - Authenticated (Administrator+) Directory Traversal","id":"CVE-2023-5504","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"path_traversal","year":"2023"},"n_packages":0,"n_references":3,"next":{"headline":"BackWPup \u003c= 4.0.1 - Authenticated (Administrator+) Directory Traversal","id":"CVE-2023-5505"},"packages":[],"prev":{"headline":"Auth bypass in EOS","id":"CVE-2023-5502"},"products":["BackWPup – WordPress Backup \u0026 Restore Plugin"],"published":"2024-01-11","related":[{"cvss_score":7.5,"headline":"BackWPup \u003c 4.0.4 - Unauthenticated Backup Download","id":"CVE-2023-7164","kev_date_added":null,"published":"2024-04-08"},{"cvss_score":7.5,"headline":"Information disclosure in backwpup","id":"CVE-2017-2551","kev_date_added":null,"published":"2017-09-27"},{"cvss_score":6.8,"headline":"BackWPup \u003c= 4.0.1 - Authenticated (Administrator+) Directory Traversal","id":"CVE-2023-5505","kev_date_added":null,"published":"2024-08-17"},{"cvss_score":2.2,"headline":"BackWPup \u003c= 4.0.2 - Plaintext Storage of Backup Destination Password","id":"CVE-2023-5775","kev_date_added":null,"published":"2024-02-24"}],"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":["wp_media"]},"summary":"Authenticated administrators can exploit directory traversal to store backups in arbitrary folders, potentially disabling other sites in shared environments.","url":"https://insights.sbomify.com/CVE-2023-5504/"}