CVE-2025-2882
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 GreenPay(tm) by Green.Money plugin for WordPress is vulnerable to Sensitive Information Exposure in versions between 3.0.0 and 3.0.9 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 GreenPay plugin for WordPress includes a publicly accessible phpinfo.php script that exposes detailed server configuration information, PHP version, loaded extensions, environment variables, and other system-level details to unauthenticated attackers.
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.
-
Confirm GreenPay plugin is installedIn WordPress admin, go to Plugins > Installed Plugins and look for 'GreenPay' or 'Greenpay Payment Gateway', or inspect the wp-content/plugins/ directory for a folder named 'greenpay' or similarAffected if The GreenPay plugin folder exists in the WordPress plugins directory
-
Locate phpinfo.php in the pluginCheck for a file named phpinfo.php inside the GreenPay plugin folder (typically wp-content/plugins/greenpay/ or similar naming)Affected if The file phpinfo.php exists within the GreenPay plugin directory
-
Verify web accessibility of phpinfo.phpAttempt to access http://[yourdomain]/wp-content/plugins/[greenpay-folder]/phpinfo.php via a web browser or curl commandAffected if The phpinfo.php file returns PHP configuration information and is reachable without authentication
-
Check plugin versionIn WordPress admin plugin list, note the installed version of GreenPay, or inspect the main plugin PHP file for a version constant or header commentAffected if The installed version is lower than 3.0.10 (the fixed version) and the phpinfo.php file is present and accessible
A user is affected if the GreenPay plugin is installed with a version below 3.0.10 and the phpinfo.php script is present in a web-accessible location, as it allows unauthenticated disclosure of server configuration details.
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 · scopedUpdate the plugin to version 3.0.10 or later, or remove the phpinfo.php file from the web-accessible directory and/or configure web server rules to deny access to this diagnostic script.
3.1.0 or later
- Log in to WordPress admin panel
- Navigate to Plugins > Installed Plugins
- Find the GreenPay by Green.Money plugin
- If an update to version 3.1.0 or later is available, click 'Update Now'
- After updating, verify the phpinfo.php file is no longer accessible at the plugin path
- If no update is available, manually delete the phpinfo.php file from the plugin directory via FTP or file manager
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation1.0 h
- Testing1.0 h
- Review / QA0.5 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-2882 — 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-2882 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