dbcve.org
Cross-site Scripting (XSS)Weakness · CWE-79

CVE-2026-3142

MEDIUM · 6.4 CVSS v3.1 Published 2026-04-08
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
70/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 Pinterest Site Verification plugin using Meta Tag plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'post_var' parameter in versions up to, and including, 1.8 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with subscriber-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.

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 Pinterest Site Verification plugin for WordPress versions up to 1.8 fails to properly sanitize the 'post_var' parameter and escape output, allowing stored XSS injection. Attackers with subscriber-level WordPress access can embed malicious JavaScript that executes when other users view affected pages.

MitigationUpdate the plugin to version 1.9 or later which includes proper input sanitization using WordPress sanitization functions (like sanitize_text_field) and output escaping (like esc_attr). Until then, restrict subscriber-level user permissions.

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

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/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. Verify plugin installation and version
    Navigate to WordPress admin > Plugins > Installed Plugins. Locate 'Pinterest Site Verification' and note the version number displayed. Compare against version 1.8 and earlier.
    Affected if Plugin is installed and version is 1.8 or lower
  2. Confirm plugin is active status
    In the Plugins screen, verify the Pinterest Site Verification plugin shows as 'Active'. Inactive plugins cannot be exploited.
    Affected if Plugin is active
  3. Locate plugin settings page
    Access the plugin settings via the WordPress admin menu (typically under Settings > Pinterest Site Verification or a dedicated Pinterest verification settings page). Identify any input fields where user-supplied data can be saved.
    Affected if Plugin has accessible settings with input fields that accept and store user data
  4. Examine stored options for injected scripts
    Query the WordPress database (wp_options table) for options containing 'pinterest' or 'verification' in the option_name field. Inspect the option_value for script tags, iframe elements, or javascript: URIs that were not intentionally added.
    Affected if Stored plugin options contain unexpected script tags or malicious payloads

The environment is affected if the Pinterest Site Verification plugin version 1.8 or lower is installed, active, and has accessible settings that utilize the post_var parameter for storing user input.

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 plugin to version 1.9 or later which includes proper input sanitization using WordPress sanitization functions (like sanitize_text_field) and output escaping (like esc_attr). Until then, restrict subscriber-level user permissions.

Recommended fix Moderate confidence

Version 1.9 or later (verify current latest version at wordpress.org/plugins/pinterest-site-verification)

  1. Check the WordPress plugin repository for the Pinterest Site Verification plugin to verify if a version newer than 1.8 is available
  2. If version 1.9 or later is available, upgrade to the latest version from the WordPress admin dashboard under Plugins > All Plugins > Update now
  3. If no fixed version is available yet, consider temporarily removing the plugin or restricting user access to the affected functionality until a patch is released
  4. Audit user accounts with subscriber-level and above access to ensure no malicious scripts have been injected

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

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