CVE-2025-2840
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 DAP to Autoresponders Email Syncing plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and including, 1.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 DAP to Autoresponders Email Syncing WordPress plugin includes a publicly accessible phpinfo.php script in all versions up to 1.0. This script exposes PHP configuration details, server environment variables, loaded extensions, and other system information that could assist attackers in reconnaissance and planning 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.
-
Verify if the DAP to Autoresponders Email Syncing plugin is installedCheck the WordPress plugins directory (wp-content/plugins/) for a folder related to this plugin. You can also list installed plugins via wp-admin > Plugins.Affected if The plugin folder exists in the WordPress plugins directory.
-
Locate the phpinfo.php file within the pluginLook for a file named phpinfo.php inside the plugin folder. Common paths include wp-content/plugins/dap-to-autoresponders-email-syncing/phpinfo.php or similar naming patterns.Affected if A phpinfo.php file exists within the plugin directory.
-
Confirm the phpinfo.php file is web-accessibleAttempt to access the suspected phpinfo.php file via a web browser or curl command using the site's URL (e.g., https://yoursite.com/wp-content/plugins/dap-to-autoresponders-email-syncing/phpinfo.php).Affected if The phpinfo.php file loads and displays PHP configuration and server environment information in the browser.
-
Verify the plugin version is 1.0 or earlierCheck the plugin's main PHP file (usually in the plugin root) for the version comment or header, or view the plugin details in WordPress admin under Plugins > Installed Plugins.Affected if The plugin version is 1.0 or any version number lower than 1.0.
Your environment is affected if the DAP to Autoresponders Email Syncing plugin (version 1.0 or earlier) is installed and a phpinfo.php file within it is publicly accessible via the web.
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.
From vendor dataRemove or restrict access to any publicly accessible phpinfo.php files on the WordPress installation to prevent information disclosure.
- Consultation2.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,456.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-2840 — 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-2840 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