dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2025-12845

HIGH · 8.8 CVSS v3.1 Published 2026-02-19
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
94/100
Remediation priority · Urgent
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
The Tablesome Table – Contact Form DB – WPForms, CF7, Gravity, Forminator, Fluent plugin for WordPress is vulnerable to unauthorized access of data that leads to privilege escalation due to a missing capability check on the get_table_data() function in versions 0.5.4 to 1.2.1. This makes it possible for authenticated attackers, with Subscriber-level access and above, to retrieve plugin table data that can expose email log information. Attackers can leverage this on sites where the table log is enabled in order to trigger a password reset and obtain the reset key.

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 Tablesome plugin for WordPress versions 0.5.4 to 1.2.1 lacks a capability check on the get_table_data() function, allowing any authenticated user with Subscriber-level access or higher to query plugin table data. This exposes email log information including password reset keys, enabling attackers to hijack accounts and escalate privileges.

MitigationUpdate the Tablesome plugin to version 1.2.2 or later which implements proper capability checks; alternatively, disable user registration and audit existing accounts until the update can be applied.

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
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/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. Verify Tablesome plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Tablesome' in the list
    Affected if Tablesome plugin appears in the installed plugins list
  2. Determine installed Tablesome version
    Click 'View Details' on the Tablesome plugin in the Plugins page, or check the plugin's main PHP file for the 'Version' header comment
    Affected if The installed version is 0.5.4, 0.5.5, 0.5.6, 0.5.7, 0.5.8, 0.5.9, 0.6.0, 0.6.1, 0.7.0, 0.8.0, 0.9.0, 1.0.0, 1.1.0, 1.1.1, 1.2.0, or 1.2.1 (any version from 0.5.4 through 1.2.1)
  3. Confirm user registration is enabled
    In WordPress admin, go to Settings > General and check 'Anyone can register' is enabled
    Affected if User registration is enabled, allowing any attacker to create a subscriber account
  4. Audit existing subscriber-level accounts
    In WordPress admin, go to Users and filter by role 'Subscriber'. Review accounts for unknown or suspicious usernames created recently
    Affected if There are subscriber accounts you did not create, especially those created recently or with admin-like usernames

A user is affected if the Tablesome plugin version is between 0.5.4 and 1.2.1 AND user registration is enabled or unexpected subscriber accounts exist on the site.

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 Tablesome plugin to version 1.2.2 or later which implements proper capability checks; alternatively, disable user registration and audit existing accounts until the update can be applied.

Recommended fix Moderate confidence

Tablesome version 1.2.2 or latest available version (any version after 1.2.1)

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate the Tablesome plugin
  4. If an update is available, click 'Update Now' to install the latest version
  5. Alternatively, navigate to Dashboard > Updates and select Tablesome to update
  6. After updating, verify the plugin is running on version 1.2.2 or later

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-12845 — 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-12845 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