dbcve.org
Cross-Site Request Forgery (CSRF)Weakness · CWE-352

CVE-2024-12170

MEDIUM · 5.4 CVSS v3.1 Published 2025-01-07
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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
The ViewMedica 9 plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 1.4.15. This is due to missing or incorrect nonce validation on the 'Viewmedica-Admin' page. This makes it possible for unauthenticated attackers to inject arbitrary SQL queries via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.

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 · moderate confidence

The ViewMedica 9 WordPress plugin lacks proper nonce validation on its admin page, allowing unauthenticated attackers to craft forged requests that execute arbitrary SQL queries. Attackers exploit this by tricking administrators into clicking malicious links, leveraging the trusted admin session to inject SQL commands.

MitigationUpdate the ViewMedica 9 plugin to version 1.4.16 or later which includes proper nonce validation. Until then, avoid clicking untrusted links while logged into the WordPress admin panel.

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
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. Confirm ViewMedica 9 plugin is installed
    Check the WordPress plugins directory at wp-content/plugins/ for a folder named 'viewmedica-9' or 'viewmedica9', or look for ViewMedica 9 in the WordPress admin under Plugins > Installed Plugins
    Affected if The plugin folder exists and the plugin appears in the WordPress plugin list
  2. Identify the installed version number
    Open the plugin's main PHP file or readme.txt file in the plugin folder and locate the version string in the plugin header comment (e.g., 'Version: 1.4.x')
    Affected if The version number found is lower than 1.4.16 (e.g., 1.4.15, 1.4.14, etc.)
  3. Verify the admin page exists and is accessible
    Log into WordPress admin and navigate to the ViewMedica 9 settings page (typically under 'ViewMedica' menu item), or check if the file vm9_admin.php exists in the plugin directory
    Affected if The admin settings page is accessible and present in the installation
  4. Check if nonce protection is missing on the admin form
    View the source code of the plugin's admin PHP file (e.g., vm9_admin.php) and look for the form handling admin actions - search for 'wp_nonce_field' or 'check_admin_referer' calls around SQL query operations
    Affected if The admin form submission lacks wp_nonce_field() or check_admin_referer() validation before executing database queries

You are affected if the ViewMedica 9 plugin is installed with a version lower than 1.4.16 and the admin page form lacks proper nonce validation for SQL operations.

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 ViewMedica 9 plugin to version 1.4.16 or later which includes proper nonce validation. Until then, avoid clicking untrusted links while logged into the WordPress admin panel.

Recommended fix High confidence

1.4.16

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate the ViewMedica 9 plugin
  4. If an update is available, click 'Update Now' to upgrade to version 1.4.16 or later
  5. Alternatively, navigate to Plugins > Add New > Upload to manually upload version 1.4.16 of the plugin
  6. After updating, verify the plugin is running version 1.4.16 or higher

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

Have this fixed 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 help mitigating

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-2024-12170 — 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-2024-12170 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