WatchtowerWordPress extension · Watchtowerhq
CVE-2022-44583
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 · uneditedUnauth. Arbitrary File Download vulnerability in WatchTowerHQ plugin <= 3.6.15 on WordPress.
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 WatchTowerHQ WordPress plugin versions 3.6.15 and below contains an unauthenticated arbitrary file download vulnerability, allowing remote attackers to retrieve sensitive files from the server by manipulating file path parameters in the plugin's download functionality.
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
WatchtowerWordPress extension
<= 3.6.15CVSS 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.
-
Check WatchtowerHQ plugin versionAccess the WordPress admin dashboard, go to Plugins > Installed Plugins, locate the WatchtowerHQ (or Watchtower) plugin, and read the version number from the plugin description. Alternatively, inspect the main plugin file (e.g., watchtowerhq.php) in wp-content/plugins/ and look for the 'Version:' header in the file comments.Affected if The installed version is 3.6.15 or lower.
-
Verify the plugin is activeIn WordPress admin, confirm the WatchtowerHQ plugin is currently activated. Or query the wp_options table: SELECT option_value FROM wp_options WHERE option_name = 'active_plugins' and the result contains 'watchtowerhq' or similar.Affected if The plugin is activated and running.
-
Identify vulnerable download endpointExamine the plugin files in wp-content/plugins/ for download-related functionality. Look for PHP files containing 'download', 'file', or path manipulation code (e.g., file_get_contents, readfile, fopen with variable file paths). Note the specific URL endpoint (e.g., admin-ajax.php?action=watchtower_download or a dedicated download.php).Affected if The plugin contains a download function that accepts a user-controllable file path parameter.
-
Test unauthenticated access to download featureSend an HTTP request to the identified download endpoint WITHOUT providing authentication credentials. Example: curl 'http://TARGET/wp-admin/admin-ajax.php?action=watchtower_download&file=../../wp-config.php' or the specific vulnerable URL pattern. Check if the server returns file contents without requiring login.Affected if The download functionality responds to unauthenticated requests and returns file contents.
A user is affected if the WatchtowerHQ plugin version is 3.6.15 or lower, the plugin is active, and the vulnerable download endpoint is 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 dataUpgrade the WatchTowerHQ plugin to a version newer than 3.6.15. If no patched version is available, disable or remove the plugin until a fix is released.
Fix this in Watchtower
Scoped from the published advisory
- Consultation1.0 h
- Implementation1.0 h
- Testing2.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,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-44583 — 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-44583 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