dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2025-39510

HIGH · 8.5 CVSS v3.1 Published 2025-08-14
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
91/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
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in ValvePress Pinterest Automatic Pin wp-pinterest-automatic allows SQL Injection.This issue affects Pinterest Automatic Pin: from n/a through < 4.19.0.

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

SQL injection vulnerability in the Pinterest Automatic Pin WordPress plugin (wp-pinterest-automatic) versions before 4.19.0 allows attackers to inject malicious SQL commands through improperly sanitized user input, potentially enabling unauthorized database access, data exfiltration, or manipulation.

MitigationUpgrade to version 4.19.0 or later to obtain the vendor patch. As a defense-in-depth measure, review and sanitize all database queries within the plugin to use parameterized queries or prepared statements.

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
Changed
Confidentiality
High
Integrity
None
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/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 the installed version of the Pinterest Automatic Pin plugin
    Navigate to WordPress Admin > Plugins > Installed Plugins, locate 'Pinterest Automatic Pin' (wp-pinterest-automatic), and note the version number displayed. Alternatively, check the plugin's main PHP file header or the plugins.php file in wp-content/plugins/
    Affected if The displayed version is any version before 4.19.0 (e.g., 4.18.x, 4.17.x, earlier versions)
  2. Verify the plugin is actively installed
    In WordPress Admin > Plugins, confirm that Pinterest Automatic Pin shows as 'Active' rather than 'Inactive' or 'Not Installed'
    Affected if The plugin is installed and activated in the WordPress environment
  3. Identify if the plugin handles user-generated board or pin data
    Access the plugin settings at Pinterest Automatic > Add New Boards or any settings page where board names, descriptions, or pin content can be entered. Check if these fields accept user input without visible sanitization indicators
    Affected if The plugin settings pages are accessible and accept user input for board names, pin descriptions, or similar fields that feed into database queries
  4. Review WordPress error logs for SQL-related errors
    Check wp-content/debug.log (if debug logging is enabled) or the server's PHP error logs for any SQL syntax errors, warnings, or unusual database errors occurring around plugin functionality
    Affected if SQL errors or warnings appear in logs that reference the wp-pinterest-automatic plugin or its database tables
  5. Check plugin database tables for unexpected modifications
    Use a database management tool (phpMyAdmin, command line) to inspect tables prefixed with wp_pinterest_automatic_ for any suspicious entries, unusual table structures, or unexpected data that may indicate exploitation
    Affected if Tables contain unexpected data, additional tables exist, or table structures have been altered without intentional admin action

A user is affected if the Pinterest Automatic Pin plugin version is below 4.19.0 and the plugin is active in the WordPress installation.

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

Upgrade to version 4.19.0 or later to obtain the vendor patch. As a defense-in-depth measure, review and sanitize all database queries within the plugin to use parameterized queries or prepared statements.

Recommended fix High confidence

4.19.0

  1. 1. Back up your WordPress site and database before making any changes.
  2. 2. Navigate to the WordPress admin dashboard > Plugins > Installed Plugins.
  3. 3. Find the 'Pinterest Automatic Pin' plugin in the list.
  4. 4. Click 'Update now' if an update is available, or manually update to version 4.19.0 or later.
  5. 5. After updating, clear any caching mechanisms and verify the plugin is functioning correctly.
  6. 6. Consider running a security scan to confirm the vulnerability is resolved.

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

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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