CVE-2019-25727
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 · uneditedWordPress Plugin ad manager wd 1.0.11 contains an arbitrary file download vulnerability that allows unauthenticated attackers to download sensitive files by manipulating the path parameter. Attackers can send GET requests to the edit.php endpoint with export=export_csv and a malicious path parameter to read arbitrary files like wp-config.php accessible to the web server.
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 confidenceA path traversal vulnerability in WordPress plugin ad manager wd 1.0.11 allows unauthenticated attackers to download arbitrary files from the server by manipulating the path parameter in GET requests to edit.php with export=export_csv. The lack of input sanitization on the path parameter enables reading sensitive files like wp-config.php containing database credentials.
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
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
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 ad manager wd plugin is installedCheck the WordPress plugins directory (wp-content/plugins/) for a folder named 'ad-manager-wd' or 'ad-manager-wd'. Alternatively, log into WordPress admin and navigate to Plugins > Installed Plugins to list all plugins.Affected if The ad manager wd plugin appears in the installed plugins list.
-
Identify installed plugin versionIn WordPress admin, go to Plugins > Installed Plugins and locate 'Ad Manager WD'. The version number is displayed below the plugin name. Alternatively, check the 'readme.txt' or 'ad-manager-wd.php' main file in the plugin directory for the 'Version' header comment.Affected if The version is 1.0.11 or earlier unpatched versions.
-
Confirm plugin is activeIn WordPress admin > Plugins > Installed Plugins, verify the 'Ad Manager WD' plugin does not have a 'Deactivate' link but rather shows it is currently active, or check the wp_options table for active_plugins option.Affected if The plugin shows as active/enabled on the site.
-
Locate vulnerable endpoint fileNavigate to the plugin directory (wp-content/plugins/ad-manager-wd/) and verify the existence of an 'edit.php' file. Also check for any export-related PHP files that handle the export=export_csv parameter.Affected if The edit.php file exists within the plugin directory and accepts the export parameter.
The environment is affected if the Ad Manager WD plugin version 1.0.11 or earlier is installed and active, with the vulnerable edit.php endpoint present and accessible for unauthenticated file download attempts.
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 dataUpdate ad manager wd to the latest patched version; if unavailable, disable or remove the plugin. Consider deploying a WAF rule to block directory traversal patterns as a temporary mitigation.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,848.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-25727 — 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-2019-25727 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