{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2023-5775 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2023-5775 yet. Limit exposure of the affected software until one is available.","what":"CVE-2023-5775 is a low-severity vulnerability in wp_media BackWPup – WordPress Backup \u0026 Restore Plugin, published on 24 Feb 2024. An attacker needs administrator access to exploit it, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2023-5775 and fix it if it is affected.\n\nWhat it is: CVE-2023-5775 is a low-severity vulnerability in wp_media BackWPup – WordPress Backup \u0026 Restore Plugin, published on 24 Feb 2024. An attacker needs administrator access to exploit it, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2023-5775 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-5775/ (Markdown: https://insights.sbomify.com/CVE-2023-5775/index.md)","id":"CVE-2023-5775","markdown":"https://insights.sbomify.com/CVE-2023-5775/index.md","name":"CVE-2023-5775","record":{"aliases":["GHSA-vqx3-p34h-gjh5"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress backup plugin","requires_auth":"high_privilege","summary":"Administrators can retrieve backup destination passwords stored in plaintext, exposing sensitive credentials to those with admin access.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Wordfence","cpe":[{"product":"backwpup","vendor":"inpsyde"}],"cvss":{"score":2.2,"severity":"low","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:L/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-256","name":"Plaintext Storage of a Password"}],"description":"The BackWPup plugin for WordPress is vulnerable to Plaintext Storage of Backup Destination Password in all versions up to, and including, 4.0.2. This is due to to the plugin improperly storing backup destination passwords in plaintext. This makes it possible for authenticated attackers, with administrator-level access, to retrieve the password from the password input field in the UI or from the options table where the password is stored.","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.2 - Plaintext Storage of Backup Destination Password","id":"CVE-2023-5775","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2023"},"n_packages":0,"n_references":2,"next":{"headline":"Post Meta Data Manager \u003c= 1.2.1 - Cross-Site Request Forgery to Post, Term, and User Meta Deletion","id":"CVE-2023-5776"},"packages":[],"prev":{"headline":"Animated Counters \u003c= 1.7 - Authenticated (Contributor+) Stored Cross-Site Scripting via Shortcode","id":"CVE-2023-5774"},"products":["BackWPup – WordPress Backup \u0026 Restore Plugin"],"published":"2024-02-24","related":[{"cvss_score":8.7,"headline":"BackWPup \u003c= 4.0.1 - Authenticated (Administrator+) Directory Traversal","id":"CVE-2023-5504","kev_date_added":null,"published":"2024-01-11"},{"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"}],"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":"Administrators can retrieve backup destination passwords stored in plaintext, exposing sensitive credentials to those with admin access.","url":"https://insights.sbomify.com/CVE-2023-5775/"}