CVE-2021-41976
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 · uneditedTad Uploader edit book list function is vulnerable to authorization bypass, thus remote attackers can use the function to amend the folder names in the book list without logging in.
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 confidenceThe Tad Uploader plugin contains an authorization bypass vulnerability in its edit book list function. Remote, unauthenticated attackers can exploit this flaw to modify folder names within the book list by directly invoking the vulnerable function without any authentication credentials.
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< 3.5.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
- None
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/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.
-
Identify if Tad Uploader plugin is installedCheck your WordPress installation's wp-content/plugins/ directory for a folder named 'tad-uploader' or 'tad uploader', or use the WordPress admin plugins list to see if 'Tad Uploader' appears in the installed plugins.Affected if The Tad Uploader plugin folder exists in the WordPress plugins directory.
-
Check the installed version of Tad UploaderIn WordPress admin, go to Plugins > Installed Plugins and locate 'Tad Uploader'. The version number is displayed below the plugin name. Alternatively, check the main plugin PHP file for a version constant or header comment.Affected if The installed version is lower than 3.5.4.
-
Verify the edit book list function is accessibleCheck the plugin source files (typically in the main PHP file or files handling 'book' or 'list' functionality) for a function handling 'edit book list' or similar naming. Attempt to access it directly via HTTP request to the corresponding admin AJAX endpoint or direct PHP call if the function is exposed without auth checks.Affected if The vulnerable function can be invoked without authentication credentials.
-
Inspect authentication checks on the edit book list functionReview the plugin code for the edit book list function. Look for calls to WordPress functions like 'check_admin_referer', 'wp_verify_nonce', 'current_user_can', or other authentication/authorization validation before executing the folder name modification logic.Affected if No authentication or authorization check is performed before allowing folder name modifications.
You are affected if Tad Uploader plugin is installed with a version lower than 3.5.4 AND the edit book list function can be accessed 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.
dbcve · scoped3.5.4
Implement proper authentication and role-based authorization checks in the edit book list function to ensure only logged-in users with appropriate permissions can modify folder names.
Tad Uploader 3.5.4
- Locate the Tad Uploader module in your XOOPS installation
- Backup your current database and files before making any changes
- Download Tad Uploader version 3.5.4 from the official XOOPS module repository or vendor
- Replace the existing Tad Uploader module files with the version 3.5.4 files
- Run any available database update scripts if included in the release
- Verify the upgrade was successful by checking the module version in your admin panel
- Test the book list edit function to confirm it now properly requires authentication
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-41976 — 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-2021-41976 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