CVE-2025-6327
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 · uneditedUnrestricted Upload of File with Dangerous Type vulnerability in KingAddons.com King Addons for Elementor king-addons allows Upload a Web Shell to a Web Server.This issue affects King Addons for Elementor: from n/a through <= 51.1.36.
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 King Addons for Elementor plugin contains an unrestricted file upload vulnerability that allows unauthenticated attackers to upload malicious PHP files (web shells) directly to the web server, achieving remote code execution and complete site compromise.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/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 checksWork through these to decide whether this CVE applies to you.
-
Confirm King Addons for Elementor is installedNavigate to WordPress admin > Plugins, or inspect the /wp-content/plugins/king-addons directory on the server file systemAffected if The plugin is present on the WordPress site
-
Identify the installed versionCheck the plugin main file (e.g., king-addons.php) for the 'Version' header, or view the version in WordPress admin > Plugins > King Addons for ElementorAffected if The version number cannot be determined or falls within an unpatched range
-
Check for suspicious uploaded PHP filesSearch the /wp-content/uploads/ directory and other writable directories for .php files, especially those with random names or unusual timestamps: find /wp-content/uploads/ -name '*.php' -type fAffected if Unexpected PHP files are found in upload directories, particularly with recent creation dates or names resembling web shells (e.g., shell.php, backdoor.php)
-
Review access logs for file upload requestsExamine web server access logs (Apache/nginx) for POST requests to typical upload endpoints that include the plugin's AJAX handlers or file upload routesAffected if Unauthenticated POST requests to upload-related endpoints are present in the logs, especially from unexpected IP addresses
A user is affected if King Addons for Elementor is installed and the version is unpatched, or if suspicious PHP files exist in upload directories indicating potential exploitation
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 dataImmediately update King Addons for Elementor to the latest version. As a temporary measure, disable the plugin or restrict web server write permissions until the patch can be applied.
- Consultation2.0 h
- Implementation1.0 h
- Testing3.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,936.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-6327 — 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-2025-6327 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