{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2025-2880 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-2880 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-2880 is a medium-severity vulnerability in Yame | Link In Bio, published on 2 May 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-2880 and fix it if it is affected.\n\nWhat it is: CVE-2025-2880 is a medium-severity vulnerability in Yame | Link In Bio, published on 2 May 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-2880 in the wild and no public exploit code.\n\nAffected product: Yame | Link In Bio. 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-2880/ (Markdown: https://insights.sbomify.com/CVE-2025-2880/index.md)","id":"CVE-2025-2880","markdown":"https://insights.sbomify.com/CVE-2025-2880/index.md","name":"CVE-2025-2880","record":{"aliases":["GHSA-8h9f-gxp7-38hg"],"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 view sensitive information via a publicly accessible phpinfo.php script in the Yame Link In Bio WordPress plugin.","user_interaction":"not_required","vuln_class":"information_disclosure"},"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-200","name":"Exposure of Sensitive Information to an Unauthorized Actor"}],"description":"The Yame | Link In Bio plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and including, 0.9.0 through the publicly accessible phpinfo.php script. This makes it possible for unauthenticated attackers to view potentially sensitive information contained in the exposed file.","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":"Yame | Link In Bio \u003c= 0.9.0 - Unauthenticated Information Exposure","id":"CVE-2025-2880","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2025"},"n_packages":0,"n_references":3,"next":{"headline":"Developer Toolbar \u003c= 1.0.3 - Unauthenticated Information Exposure","id":"CVE-2025-2881"},"packages":[],"prev":{"headline":"Mali GPU Kernel Driver allows improper GPU processing operations","id":"CVE-2025-2879"},"products":["Yame | Link In Bio"],"published":"2025-05-02","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":["yame"]},"summary":"Unauthenticated attackers can view sensitive information via a publicly accessible phpinfo.php script in the Yame Link In Bio WordPress plugin.","url":"https://insights.sbomify.com/CVE-2025-2880/"}