Download MonitorWordPress extension · Wpchill
CVE-2022-45354
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 · uneditedExposure of Sensitive Information to an Unauthorized Actor vulnerability in WPChill Download Monitor.This issue affects Download Monitor: from n/a through 4.7.60.
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 · moderate confidenceThis is an information disclosure vulnerability in the Download Monitor WordPress plugin that allows unauthorized actors to access sensitive information. The vulnerability exists in versions through 4.7.60 and could expose sensitive data related to downloadable files or user information.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
Download MonitorWordPress extension
<= 4.7.60CVSS 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
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/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 Download Monitor plugin is installedNavigate to WordPress admin dashboard > Plugins > Installed Plugins. Look for 'Download Monitor' or 'Wpchill Download Monitor' in the plugin list.Affected if The plugin appears in the installed plugins list
-
Check installed plugin versionIn the plugin list, click on the plugin or view the plugin details to find the version number. Alternatively, inspect the plugin main file header in wp-content/plugins/download-manager/ or similar path.Affected if Version is 4.7.60 or lower, or version cannot be determined (indicating outdated installation)
-
Inspect plugin settings for public accessGo to Downloads > Settings in WordPress admin. Check if any download links or file information pages are publicly accessible without authentication.Affected if Download links or file metadata are accessible to unauthenticated users
-
Review download log or access logsCheck WordPress debug logs or server access logs for unusual requests to download-monitor endpoints that may indicate exploitation attempts.Affected if Unexpected access patterns to download-monitor related URLs from unauthenticated sources
You are affected if Download Monitor plugin version 4.7.60 or lower is installed and downloads or sensitive file information are accessible 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.
From vendor dataUpdate Download Monitor plugin to the latest patched version. If no update is available, consider disabling the plugin or implementing additional access controls on the affected functionality.
Fix this in Download Monitor
Scoped from the published advisory
- Consultation1.0 h
- Implementation1.0 h
- Testing1.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-2022-45354 — 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-2022-45354 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