{"answers":{"affected":"","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-7385 exists.","fix":"No fix has been published for CVE-2026-7385 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-7385 is a medium-severity vulnerability in Unknown Decent Comments, published on 20 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-7385 and fix it if it is affected.\n\nWhat it is: CVE-2026-7385 is a medium-severity vulnerability in Unknown Decent Comments, published on 20 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-7385 exists.\n\nAffected product: Unknown Decent Comments. 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-2026-7385/ (Markdown: https://insights.sbomify.com/CVE-2026-7385/index.md)","id":"CVE-2026-7385","markdown":"https://insights.sbomify.com/CVE-2026-7385/index.md","name":"CVE-2026-7385","record":{"aliases":["GHSA-77v2-rrqg-jjqc"],"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":"Unauthenticated attackers can enumerate registered user email addresses via the REST API, exposing sensitive user data.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"WPScan","cpe":[],"cvss":{"score":5.8,"severity":"medium","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:N/A:N","version":"3.1"},"cwes":[],"description":"The Decent Comments WordPress plugin before 3.0.2 does not restrict access to comment author email addresses and post author email addresses via its REST API endpoint, allowing unauthenticated attackers to enumerate registered user email addresses.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":null,"headline":"Decent Comments \u003c 3.0.2 - Unauthenticated Email Address Disclosure","id":"CVE-2026-7385","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"fatbobman mail-mcp-bridge mail_mcp_server.py path traversal","id":"CVE-2026-7386"},"packages":[],"prev":{"headline":"ezequiroga mcp-bases research_server.py search_papers path traversal","id":"CVE-2026-7384"},"products":["Decent Comments"],"published":"2026-05-20","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-05-20","vendors":["Unknown"]},"summary":"Unauthenticated attackers can enumerate registered user email addresses via the REST API, exposing sensitive user data.","url":"https://insights.sbomify.com/CVE-2026-7385/"}