{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2025-6792 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-6792 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-6792 is a medium-severity missing authorization vulnerability in amentotechpvtltd One to one user Chat by WPGuppy, published on 14 Feb 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-2025-6792 and fix it if it is affected.\n\nWhat it is: CVE-2025-6792 is a medium-severity missing authorization vulnerability in amentotechpvtltd One to one user Chat by WPGuppy, published on 14 Feb 2026. 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-2025-6792 in the wild and no public exploit code.\n\nAffected product: amentotechpvtltd One to one user Chat by WPGuppy. 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-2025-6792/ (Markdown: https://insights.sbomify.com/CVE-2025-6792/index.md)","id":"CVE-2025-6792","markdown":"https://insights.sbomify.com/CVE-2025-6792/index.md","name":"CVE-2025-6792","record":{"aliases":["GHSA-h9rw-4pm8-962h"],"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 intercept and view private chat messages due to a missing capability check in the REST API endpoint.","user_interaction":"not_required","vuln_class":"missing_authorization"},"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-306","name":"Missing Authentication for Critical Functionality"}],"description":"The One to one user Chat by WPGuppy plugin for WordPress is vulnerable to unauthorized access of data due to a missing capability check on the /wp-json/guppylite/v2/channel-authorize rest endpoint in all versions up to, and including, 1.1.4. This makes it possible for unauthenticated attackers to intercept and view private chat messages between users.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":"2026-03-23","github_poc":1,"max_poc_stars":0,"metasploit":0,"nuclei":0,"refs":[{"date":"2026-03-23T15:06:37Z","kind":"github_poc","ref":"https://github.com/jFriedli/CVE-2025-6792","stars":0,"title":null}],"tier":"poc_unverified"},"has_fix":null,"headline":"One to one user Chat by WPGuppy \u003c= 1.1.4 - Unauthenticated Information Disclosure via Chat Message Interception","id":"CVE-2025-6792","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"missing_authorization","year":"2025"},"n_packages":0,"n_references":2,"next":{"headline":"Path traversal in QConvergeConsole","id":"CVE-2025-6793"},"packages":[],"prev":{"headline":"Second order SQL injection available to user with low privilege","id":"CVE-2025-6791"},"products":["One to one user Chat by WPGuppy"],"published":"2026-02-14","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)"},{"class":"open","licence":"CC0","name":"PoC-in-GitHub"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-04-08","vendors":["amentotechpvtltd"]},"summary":"Unauthenticated attackers can intercept and view private chat messages due to a missing capability check in the REST API endpoint.","url":"https://insights.sbomify.com/CVE-2025-6792/"}