FilebirdWordPress extension · Ninjateam
CVE-2024-35166
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 Ninja Team Filebird.This issue affects Filebird: from n/a through 5.6.3.
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 confidenceAn information disclosure vulnerability in Ninja Team Filebird plugin (versions up to 5.6.3) allows unauthorized actors to access sensitive data. The specific nature of the exposed information is not detailed in the available description, but the CVSS 7.5 score indicates significant exposure of confidential data.
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
FilebirdWordPress extension
< 5.6.4CVSS 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.
-
Confirm Filebird plugin is installedCheck your WordPress plugins directory for the Filebird plugin folder, typically at wp-content/plugins/filebird, or view it in the WordPress admin Plugins pageAffected if The plugin folder filebird exists in the plugins directory
-
Identify the installed Filebird versionOpen the main plugin file (filebird.php) or the readme.txt file in the filebird plugin folder and locate the version declaration comment (e.g., Version: x.x.x)Affected if The version number shown is below 5.6.4 (e.g., 5.6.3, 5.6.2, etc.)
-
Check plugin status and accessibilityIn WordPress admin, verify if the Filebird plugin is activated. If activated, note that the vulnerable code path may be reachableAffected if The plugin is currently activated and the version is below 5.6.4
You are affected if the Filebird plugin is installed and the installed version is any version below 5.6.4.
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 · scoped5.6.4
Update Filebird to the latest version once available, or apply vendor-supplied patches. If immediate patching is not possible, restrict access to the plugin's admin interfaces and AJAX endpoints via server-side access controls.
Filebird 5.6.4
- 1. Backup your WordPress site and database before updating any plugin.
- 2. Navigate to Plugins > Installed Plugins in your WordPress admin dashboard.
- 3. Locate Filebird in the plugin list.
- 4. If an update is available, click 'Update Now' to update Filebird to version 5.6.4 or later.
- 5. After updating, verify the plugin is functioning correctly and test file management features.
- 6. Confirm the new version number reflects 5.6.4 or higher in the plugins list.
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Filebird
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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 $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-35166 — 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-2024-35166 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