CVE-2025-2880
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedThe 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe Yame | Link In Bio WordPress plugin ships with a publicly accessible phpinfo.php script that exposes server configuration details, PHP version, loaded extensions, environment variables, and potentially sensitive system paths. Unauthenticated attackers can access this file directly via the web to gather reconnaissance information.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Verify Yame Link In Bio plugin is installedCheck the WordPress plugins directory for the Yame | Link In Bio plugin, or query the WordPress database wp_plugins table for this pluginAffected if The plugin is present on the WordPress installation
-
Locate phpinfo.php in plugin directorySearch for phpinfo.php files within the plugin directory structure, typically found in /wp-content/plugins/yame-link-in-bio/ or similar pathAffected if A phpinfo.php file exists within the plugin folder
-
Test public web access to phpinfo.phpAttempt to access the file via HTTP request at the expected URL path such as /wp-content/plugins/yame-link-in-bio/phpinfo.phpAffected if The file is accessible without authentication and returns PHP configuration output
-
Confirm phpinfo output is presentInspect the HTTP response - a vulnerable file will display a standard phpinfo() page showing PHP version, loaded extensions, and server configurationAffected if The response contains a standard phpinfo page with server and PHP details
If the Yame | Link In Bio plugin is installed AND the phpinfo.php file is publicly accessible via web, the environment is affected by this CVE.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scopedRemove or delete the phpinfo.php file from the web root/public_html directory, or restrict access via .htaccess rules to prevent unauthorized access.
Latest available version of Yame | Link In Bio plugin (version higher than 0.9.0)
- Navigate to the WordPress admin dashboard
- Go to Plugins > Installed Plugins
- Locate the 'Yame | Link In Bio' plugin
- If an update is available, click 'Update Now'
- After updating, verify the phpinfo.php file is no longer publicly accessible by attempting to access it via the browser
- If the plugin has no update available, consider temporarily disabling the plugin until a security update is released, or remove the plugin if not needed
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation1.0 h
- Testing1.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-2880 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-2880 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data