dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2025-12895

MEDIUM · 5.3 CVSS v3.1 Published 2026-01-15
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/100
Remediation priority · Elevated
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 Kalium 3 | Creative WordPress & WooCommerce Theme theme for WordPress is vulnerable to unauthorized email sending due to a missing capability check on the kalium_vc_contact_form_request() function in all versions up to, and including, 3.29. This makes it possible for unauthenticated attackers to use the theme an an open mail relay and send email to arbitrary email addresses on the server's behalf.

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 Kalium theme for WordPress contains a contact form processing function (kalium_vc_contact_form_request) that lacks proper capability checks, allowing unauthenticated users to submit emails through the server. This turns the site into an open mail relay, enabling spam distribution and potential reputation damage.

MitigationUpdate the Kalium theme to version 3.30 or later which includes the missing capability check. Until patched, consider disabling the contact form functionality or implementing a web application firewall rule to block unauthorized contact form submissions.

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
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 checks

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

  1. Verify Kalium theme is installed
    Inspect the wp-content/themes directory or check via WordPress admin under Appearance > Themes to confirm the Kalium theme is active or installed.
    Affected if Kalium theme is present on the WordPress site
  2. Check installed Kalium theme version
    Locate the style.css file in the Kalium theme directory and read the Version header, or check via WordPress admin theme details panel.
    Affected if Version is earlier than 3.30 (versions prior to 3.30 lack the capability check)
  3. Confirm contact form functionality is present
    Search for the function kalium_vc_contact_form_request in the theme files (typically in includes/ or lib/ directories), or check if any contact form pages or elements using this function exist on the site.
    Affected if The kalium_vc_contact_form_request function exists in the theme code
  4. Verify contact form is publicly accessible
    Attempt to access a page containing the Kalium contact form element, or inspect the theme for Visual Composer/WPBakery contact form shortcodes that invoke this function. No authentication should be required to submit.
    Affected if The contact form is exposed to unauthenticated users without capability verification in the code

You are affected if the Kalium theme is installed with a version earlier than 3.30 and the contact form functionality using kalium_vc_contact_form_request is present and accessible to unauthenticated users.

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 the Kalium theme to version 3.30 or later which includes the missing capability check. Until patched, consider disabling the contact form functionality or implementing a web application firewall rule to block unauthorized contact form submissions.

Recommended fix High confidence

Kalium 3.30 or later

  1. 1. Navigate to your WordPress dashboard and go to Appearance > Themes
  2. 2. Locate the Kalium theme in your installed themes
  3. 3. Check the current version number of the Kalium theme
  4. 4. If the version is 3.29 or lower, update the theme to version 3.30 or later
  5. 5. Alternatively, download the latest version of Kalium from the theme vendor (ThemeForest or Laborator's official site) and upload it via WordPress theme uploader
  6. 6. After updating, verify the kalium_vc_contact_form_request() function now includes proper capability checks (nonce verification or authorization validation)
Caveat Theme updates may include breaking changes; review the theme changelog before upgrading

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

Have this fixed Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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