dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2026-6674

MEDIUM · 6.5 CVSS v3.1 Published 2026-04-21
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
The Plugin: CMS für Motorrad Werkstätten plugin for WordPress is vulnerable to SQL Injection via the 'arttype' parameter in all versions up to, and including, 1.0.0 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. This makes it possible for authenticated attackers, with subscriber-level access and above, to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database.

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 CMS für Motorrad Werkstätten WordPress plugin up to version 1.0.0 contains a SQL Injection vulnerability in the 'arttype' parameter. Authenticated attackers with subscriber-level access can inject malicious SQL queries due to insufficient input escaping and lack of prepared statements in the SQL query execution, allowing extraction of sensitive database information.

MitigationUpdate the plugin to the latest version when available. If no patch exists, disable and replace the plugin. For immediate remediation, implement $wpdb->prepare() or parameterized queries for the 'arttype' parameter and ensure all user inputs are properly sanitized before SQL execution.

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. Confirm the plugin is installed
    Check the WordPress plugins directory for 'cms-fur-motorrad-werkstatten' or 'cms-fur-motorrad-werkstaetten' folder, or list installed plugins via wp-cli: wp plugin list --status=active --format=csv
    Affected if The plugin appears in the list of active or installed plugins on the WordPress site
  2. Identify the installed plugin version
    Read the plugin header from the main plugin PHP file (usually in wp-content/plugins/[plugin-folder]/cms-fur-motorrad-werkstatten.php) or run: wp plugin get cms-fur-motorrad-werkstatten --field=version
    Affected if The version is 1.0.0 or lower (the vulnerability affects up to version 1.0.0)
  3. Locate code using the 'arttype' parameter
    Search the plugin directory for occurrences of 'arttype' in PHP files: grep -r 'arttype' /path/to/wp-content/plugins/[plugin-folder]/ or use a file search in the plugin editor
    Affected if Code references the 'arttype' parameter without using $wpdb->prepare() or parameterized queries around that parameter
  4. Check if the vulnerable endpoint is accessible
    Examine the code containing 'arttype' to determine which WordPress hook or page loads it (such as init, admin_init, or a shortcode). Verify if any access control restricts subscriber-level users from reaching this code path.
    Affected if The code processes 'arttype' from $_GET, $_POST, or $_REQUEST and can be reached by users with subscriber role or higher
  5. Verify lack of SQL preparation
    Review the SQL query using 'arttype' - check that it does NOT use $wpdb->prepare() with placeholders (%s, %d) and does NOT use parameterized/bound queries. The query should directly concatenate or interpolate the 'arttype' input.
    Affected if The SQL query embeds 'arttype' directly into the query string without sanitization or prepared statement usage

A user is affected if the CMS für Motorrad Werkstätten plugin version 1.0.0 or lower is active and contains code that processes the 'arttype' parameter in SQL queries without using prepared statements.

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 the latest version when available. If no patch exists, disable and replace the plugin. For immediate remediation, implement $wpdb->prepare() or parameterized queries for the 'arttype' parameter and ensure all user inputs are properly sanitized before SQL execution.

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-2026-6674 — 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-2026-6674 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