dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2023-45275

MEDIUM · 6.5 CVSS v3.1 Published 2025-01-02
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable 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
Missing Authorization vulnerability in WP Chill Kali Forms kali-forms allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Kali Forms: from n/a through <= 2.3.28.

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 confidence

Missing authorization vulnerability in the Kali Forms WordPress plugin allows attackers to exploit incorrectly configured access control security levels. The vulnerability stems from improper access control checks in the plugin, potentially allowing unauthorized users to access or modify form data or plugin functionality they should not have permission to access.

MitigationUpdate Kali Forms to the latest version which should contain proper authorization checks, or implement role-based access control (RBAC) and capability checks on all plugin endpoints and functions.

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/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 checks

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

  1. Identify if Kali Forms plugin is installed
    Log into WordPress admin panel and navigate to Plugins > Installed Plugins. Look for 'Kali Forms' in the list of active plugins.
    Affected if Kali Forms plugin appears in the installed plugins list
  2. Determine installed Kali Forms version
    In the Plugins list, find Kali Forms and view the version number displayed beneath the plugin name. Alternatively, access the plugin files via FTP or file manager and check the main plugin PHP file header for 'Version' tag.
    Affected if A version number is displayed for Kali Forms
  3. Compare your version to known vulnerable releases
    Research the specific version history of Kali Forms for CVE-2023-45275. Check the plugin's changelog or security advisories for the exact version ranges reported as vulnerable.
    Affected if Your installed version falls within a version range known to contain the authorization flaw
  4. Verify unauthorized endpoint access potential
    As an administrator, temporarily create a low-privilege user role (subscriber or contributor) and test whether that user can access Kali Forms settings, form submissions, or export features that should require admin capabilities.
    Affected if A low-privilege user can access plugin functions or data without proper capability checks
  5. Audit plugin capability configurations
    Review the Kali Forms plugin directory for capability checks. Examine PHP files for current_user_can() or role-based access control implementations around form handling, submission export, and settings modification functions.
    Affected if No capability checks or weak checks are found protecting sensitive plugin functions

Your environment is affected if Kali Forms is installed AND your version lacks the authorization fix AND low-privilege users can access restricted plugin functionality.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update Kali Forms to the latest version which should contain proper authorization checks, or implement role-based access control (RBAC) and capability checks on all plugin endpoints and functions.

Recommended fix Moderate confidence

Latest available version of Kali Forms (greater than 2.3.28)

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate the Kali Forms plugin in the list
  4. Check the current installed version (should be <= 2.3.28)
  5. Click on 'Update now' if an update is available, or manually download the latest version from the WordPress plugin repository
  6. After updating, verify the new version number in the plugins list
  7. Test that the Kali Forms functionality works correctly and that the access control vulnerability is resolved
Caveat Review the plugin's changelog for any breaking changes between your current version and the latest version before updating in production environments

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-45275 — 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-2023-45275 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