dbcve.org
Improper Input ValidationWeakness · CWE-20

CVE-2025-1514

HIGH · 7.3 CVSS v3.1 Published 2025-03-26
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
82/100
Remediation priority · High
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 Active Products Tables for WooCommerce. Use constructor to create tables plugin for WordPress is vulnerable to unauthorized filter calling due to insufficient restrictions on the get_smth() function in all versions up to, and including, 1.0.6.7. This makes it possible for unauthenticated attackers to call arbitrary WordPress filters with a single parameter.

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 Active Products Tables for WooCommerce plugin has an unprotected get_smth() function that lacks proper authorization and input validation checks. This allows unauthenticated attackers to invoke arbitrary WordPress filters with a single parameter, enabling privilege escalation and potentially facilitating secondary attacks like XSS or SQL injection through filter manipulation.

MitigationUpdate the plugin to version 1.0.7 or later which contains the security fix. If no update is available, consider removing the plugin until a patched version is released.

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
Low
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L

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 plugin installation
    Navigate to WordPress admin dashboard > Plugins and look for 'Active Products Tables for WooCommerce' in the installed plugins list
    Affected if plugin is installed and active
  2. Check installed plugin version
    In the Plugins page, locate the plugin and hover over or click to view the version number. Alternatively, check the plugin's main PHP file header for 'Version:' tag
    Affected if version is present but lower than 1.0.7
  3. Confirm plugin is active
    On the Plugins page, verify the plugin status shows 'Active' under the plugin name
    Affected if plugin is active and version is below 1.0.7
  4. Verify WordPress exposes the vulnerable endpoint
    Attempt a curl request to check if the plugin's AJAX endpoint responds: curl -s -X POST https://yourdomain.com/wp-admin/admin-ajax.php -d 'action=get_smth&param=test' (replace yourdomain.com)
    Affected if the request returns a response without requiring authentication

If the Active Products Tables for WooCommerce plugin is installed, active, and running on a version before 1.0.7, the environment is affected by this CVE and the unprotected get_smth() function is accessible to unauthenticated attackers.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the plugin to version 1.0.7 or later which contains the security fix. If no update is available, consider removing the plugin until a patched version is released.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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