dbcve.org
KaswaraWordPress extension · Kaswara Project

CVE-2021-4448

CRITICAL · 9.8 CVSS v3.1 Published 2024-10-16
Fix available
A fix is available. Upgrade to after 3.0.1 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 · unedited
The Kaswara Modern VC Addons plugin for WordPress is vulnerable to authorization bypass in versions up to, and including, 3.0.1 due to insufficient capability checking on various AJAX actions. This makes it possible for unauthenticated attackers to perform a wide variety of unauthorized actions such as importing data, uploading arbitrary files, deleting arbitrary files, and more.

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 confidence

The Kaswara Modern VC Addons WordPress plugin versions up to 3.0.1 contains vulnerable AJAX action handlers that lack proper capability verification, allowing unauthenticated attackers to invoke sensitive functions including data import, arbitrary file upload, and arbitrary file deletion.

MitigationUpdate to the latest patched version of the plugin; if no patched version is available, remove the plugin immediately and assess for any compromise.

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
KaswaraWordPress extension
Affected:<= 3.0.1

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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm Kaswara plugin is installed
    Check for the plugin directory at /wp-content/plugins/kaswara-modern-vc-addons/ or look for 'Kaswara Modern VC Addons' in WordPress admin under Plugins
    Affected if The plugin directory or listing exists on the WordPress site
  2. Identify installed plugin version
    View the plugin main file (usually kaswara-modern-vc-addons.php) and locate the 'Version:' header in the file comments, or check the plugin admin page for the version number
    Affected if The installed version is 3.0.1 or lower
  3. Verify AJAX endpoint is accessible
    Check if /wp-admin/admin-ajax.php responds to requests. This endpoint is required for the plugin's AJAX functionality and is the attack vector for this vulnerability
    Affected if The AJAX endpoint returns a valid response (HTTP 200) and is accessible without authentication
  4. Confirm plugin AJAX handlers are registered
    Examine the plugin's main PHP file for wp_ajax_ and wp_ajax_nopriv_ hooks that register the plugin's AJAX actions. These handlers lack the capability checks mentioned in the CVE
    Affected if AJAX action hooks like 'kaswara_import_data', 'kaswara_upload_file', or similar file operation functions are registered without proper authorization checks

If the Kaswara Modern VC Addons plugin is installed with version 3.0.1 or lower and the AJAX endpoint is accessible, the site is vulnerable to unauthenticated arbitrary file operations and data import via the insecure AJAX handlers.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to a release after 3.0.1
Interim mitigation

Update to the latest patched version of the plugin; if no patched version is available, remove the plugin immediately and assess for any compromise.

Recommended fix Moderate confidence

Latest version after 3.0.2 (check WordPress plugin repository or vendor for current release)

  1. 1. Navigate to the WordPress admin dashboard
  2. 2. Go to Plugins > Installed Plugins
  3. 3. Locate 'Kaswara Modern VC Addons' in the plugin list
  4. 4. If an update is available, click 'Update Now' to upgrade to the latest version
  5. 5. If no update is available through WordPress, manually download the latest version from a trusted source (such as the official WordPress plugin repository or CodeCanyon)
  6. 6. After updating, verify that the plugin is functioning correctly on the site

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Kaswara Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,090
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,744.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2021-4448 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2021-4448 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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