CVE-2025-2841
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 Cart66 Cloud plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and including, 2.3.7 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 Cart66 Cloud WordPress plugin includes a publicly accessible phpinfo.php script that exposes sensitive server configuration information, including PHP version, loaded extensions, server paths, and environment variables. Unauthenticated attackers can access this diagnostic file to gather information useful for targeting further attacks.
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.
-
Identify if Cart66 Cloud plugin is installedCheck the WordPress plugins directory (wp-content/plugins/) for a folder named 'cart66-cloud' or similar. In WordPress admin, go to Plugins > Installed Plugins and look for Cart66 Cloud.Affected if Cart66 Cloud plugin is present on the WordPress site
-
Locate the plugin directory pathNavigate to wp-content/plugins/ in the WordPress installation and identify the exact folder name for the Cart66 Cloud plugin.Affected if The plugin folder exists on the server
-
Check if phpinfo.php exists in the plugin directoryLook for a file named phpinfo.php inside the Cart66 Cloud plugin folder. This can be done via FTP, SSH, or file manager: list files in the plugin directory.Affected if The file phpinfo.php exists within the Cart66 Cloud plugin folder
-
Verify public accessibility of phpinfo.phpAttempt to access the file via HTTP request (e.g., visit https://yourdomain.com/wp-content/plugins/cart66-cloud/phpinfo.php or similar path) without any authentication. Check if the request returns HTTP 200 and displays PHP configuration information.Affected if The phpinfo.php file returns a 200 OK response and displays PHP version and configuration details to unauthenticated users
A user is affected if the Cart66 Cloud plugin is installed and its phpinfo.php file is publicly accessible over the web without authentication.
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 restrict public access to the phpinfo.php file within the plugin directory to prevent unauthenticated information disclosure.
2.3.8
- Update the Cart66 Cloud WordPress plugin to version 2.3.8 or later
- Verify that the phpinfo.php file is no longer publicly accessible by navigating to /phpinfo.php on your site and confirming it returns a 404 or requires authentication
- If the file still exists, manually delete the phpinfo.php file from the plugin directory as a secondary precaution
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-2841 — 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-2841 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