dbcve.org
Cpt BaseWordPress extension · Kubiq

CVE-2022-29431

MEDIUM · 5.4 CVSS v3.1 Published 2022-05-20
Fix available
A fix is available. Upgrade to after 5.8 or later.
See remediation →
61/100
Remediation priority · Elevated
Remotely reachable No privileges

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
Cross-Site Request Forgery (CSRF) vulnerability in KubiQ CPT base plugin <= 5.8 at WordPress allows an attacker to delete the CPT base.

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

Cross-Site Request Forgery (CSRF) vulnerability in KubiQ CPT base plugin for WordPress (versions 5.8 and below) allows attackers to trick authenticated administrators into deleting the Custom Post Type base configuration by forging malicious requests that the vulnerable application accepts without proper token validation.

MitigationImplement WordPress nonce tokens on the delete CPT base action and verify the nonce server-side before processing the request; also validate the HTTP Referer header to ensure requests originate from the legitimate admin interface.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Cpt BaseWordPress extension
Affected:<= 5.8

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
Required
Scope
Unchanged
Confidentiality
None
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/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. Check if KubiQ CPT base plugin is installed
    Navigate to WordPress admin dashboard > Plugins and look for 'Kubiq Cpt Base' in the installed plugins list, or inspect the plugins directory for the kubiq-cpt-base folder
    Affected if the plugin is present in the WordPress installation
  2. Determine installed plugin version
    In WordPress admin > Plugins > Installed Plugins, find 'Kubiq Cpt Base' and read the version number displayed below the plugin name; alternatively, open the main plugin file (e.g., /wp-content/plugins/kubiq-cpt-base/index.php) and check the 'Version' header in the plugin comment block
    Affected if the version number is 5.8 or lower
  3. Verify the delete CPT base functionality exists
    Access the plugin settings page in WordPress admin (usually under Settings or a dedicated KubiQ menu) and locate any option to delete or reset the Custom Post Type base configuration
    Affected if the delete CPT base configuration option is present and accessible to administrators
  4. Inspect delete action for nonce validation
    Locate the PHP handler that processes the delete CPT base request (typically in the main plugin file or an admin class); search for 'nonce' or 'wp_verify_nonce' calls within the function handling the delete action
    Affected if the delete handler does not contain a nonce verification call or the nonce check can be bypassed

If the KubiQ CPT base plugin is installed at version 5.8 or below and the delete CPT base feature exists, the environment is vulnerable to CVE-2022-29431 because requests lack proper CSRF token validation.

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
Upgrade available Upgrade to a release after 5.8
Interim mitigation

Implement WordPress nonce tokens on the delete CPT base action and verify the nonce server-side before processing the request; also validate the HTTP Referer header to ensure requests originate from the legitimate admin interface.

Recommended fix Moderate confidence

Cpt Base version > 5.8 (verify exact version on wordpress.org)

  1. Check the WordPress plugin repository at wordpress.org for the Cpt Base plugin to identify if a version newer than 5.8 is available
  2. If a newer version exists, update the plugin through WordPress admin or via wp-cli: wp plugin update cpt-base
  3. Verify the update was successful and test that CPT functionality works as expected
  4. Review the plugin's changelog to confirm the CSRF fix is included in the new version

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

Fix this in Cpt Base Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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