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

CVE-2026-6702

MEDIUM · 6.1 CVSS v3.1 Published 2026-05-05
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
68/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 Publish 2 Ping.fm plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 1.1. This is due to missing or incorrect nonce validation on the '/wp-admin/options-general.php?page=admin.php' page. This makes it possible for unauthenticated attackers to update settings and inject malicious web scripts 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 · high confidence

The Publish 2 Ping.fm WordPress plugin lacks proper nonce validation on its admin settings page (/wp-admin/options-general.php?page=admin.php), allowing attackers to forge administrative requests. Successful exploitation enables unauthorized modification of plugin settings and injection of malicious scripts via cross-site request forgery.

MitigationRemove or replace the unmaintained plugin, as no patched version is available. If continued use is required, manually add nonce verification to all form submissions and actions in the plugin code.

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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 if Publish 2 Ping.fm plugin is installed
    Navigate to WordPress admin dashboard, go to Plugins > Installed Plugins, and search for 'Publish 2 Ping.fm' or 'ping.fm'. Check if the plugin appears in the list and note whether it is activated.
    Affected if The plugin is present and activated in the WordPress installation.
  2. Locate plugin files and identify version
    Access the wp-content/plugins directory via file manager or FTP. Look for a folder named 'publish-2-ping-fm' or similar. Open any readme.txt or plugin main file to find the declared version number.
    Affected if The plugin files exist and a version number is found in the plugin header.
  3. Inspect admin settings file for nonce implementation
    Open the plugin file handling the admin settings page (typically admin.php or similar in the plugin folder). Search for 'wp_nonce_field', 'wp_verify_nonce', 'check_admin_referer', or 'nonce' within form handling code on the options-general.php page route.
    Affected if The settings form submission code lacks nonce verification functions, or nonce checks are missing entirely.
  4. Verify settings page is accessible
    Attempt to access /wp-admin/options-general.php?page=admin.php while logged in as administrator. Confirm the page loads and displays plugin configuration options.
    Affected if The plugin settings page loads without requiring additional security tokens beyond normal admin authentication.
  5. Compare installed version to any known unaffected versions
    If a version number was found in step 2, search for any official release notes or changelog indicating when nonce validation was added. Without official patched version info, treat all versions as potentially affected.
    Affected if No patched version information exists, indicating the vulnerability may persist in the current installation.

A user is affected if the Publish 2 Ping.fm plugin is installed and its admin settings code does not implement nonce validation for form submissions.

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

Remove or replace the unmaintained plugin, as no patched version is available. If continued use is required, manually add nonce verification to all form submissions and actions in the plugin code.

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-6702 — 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-6702 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