{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2025-6003 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-6003 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-6003 is a medium-severity missing authorization vulnerability in cyberlord92 WordPress Single Sign-On (SSO) - Multisite All-Inclusive, published on 12 Jun 2025. 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-6003 and fix it if it is affected.\n\nWhat it is: CVE-2025-6003 is a medium-severity missing authorization vulnerability in cyberlord92 WordPress Single Sign-On (SSO) - Multisite All-Inclusive, published on 12 Jun 2025. 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-6003 in the wild and no public exploit code.\n\nAffected product: cyberlord92 WordPress Single Sign-On (SSO) - Multisite All-Inclusive. 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-6003/ (Markdown: https://insights.sbomify.com/CVE-2025-6003/index.md)","id":"CVE-2025-6003","markdown":"https://insights.sbomify.com/CVE-2025-6003/index.md","name":"CVE-2025-6003","record":{"aliases":["GHSA-p4cv-qgmg-7q4w"],"analysis":{"component_type":"cms_plugin","fix_type":"patch","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress SSO plugin","requires_auth":"none","summary":"Unauthenticated attackers can extract sensitive restricted site content due to incorrect authorization checks in the WordPress Single Sign-On plugin.","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-863","name":"Incorrect Authorization"}],"description":"The WordPress Single Sign-On (SSO) plugin for WordPress is vulnerable to unauthorized access due to a misconfigured capability check on a function in all versions up to, and including, the *.5.3 versions of the plugin. This makes it possible for unauthenticated attackers to extract sensitive data including site content that has been restricted to certain users and/or roles.","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":"WordPress Single Sign-On (SSO) - Multiple Versions - Incorrect Authorization to Sensitive Information Exposure","id":"CVE-2025-6003","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":"Vault Userpass and LDAP User Lockout Bypass","id":"CVE-2025-6004"},"packages":[],"prev":{"headline":"VirtueMart - Unrestricted File Upload","id":"CVE-2025-6002"},"products":["WordPress Single Sign-On (SSO) - Multisite All-Inclusive","WordPress Single Sign-On (SSO) - Multisite Enterprise","WordPress Single Sign-On (SSO) - Multisite Premium","WordPress Single Sign-On (SSO) - Single Site All-Inclusive","WordPress Single Sign-On (SSO) - Single Site Enterprise","WordPress Single Sign-On (SSO) - Single Site Premium","WordPress Single Sign-On (SSO) - Single Site Standard"],"published":"2025-06-12","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":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-04-08","vendors":["cyberlord92"]},"summary":"Unauthenticated attackers can extract sensitive restricted site content due to incorrect authorization checks in the WordPress Single Sign-On plugin.","url":"https://insights.sbomify.com/CVE-2025-6003/"}