CVE-2026-6702 MEDIUM

CVE-2026-6702: Publish 2 Ping.fm <= 1.1 - Cross-Site Request Forgery to Stored Cross-Site Scripting via 'wpPingPingKey' Parameter

Vendor Foux
Product Publish 2 Ping.fm
Weakness CWE-352 · CSRF
Published May 5, 2026
Last update May 5, 2026

CVSS base score

6.1/10
Attack vector Network
Attack complexity Low
Privileges required None
User interaction Required
Confidentiality Low
Integrity Low

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N

What the vulnerability does

01Description

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.

Explanation of Vulnerability in Simple Terms

02Summary

Publish 2 Ping.fm versions 1.1 and earlier are vulnerable to cross-site request forgery (CSRF). An attacker can craft a malicious webpage that, when visited by a logged-in site administrator, performs unwanted actions on the site without their knowledge. The vulnerability requires user interaction—the admin must visit the attacker's page—but can affect the site's integrity and confidentiality.

What an attacker can do

03Attacker Capabilities

Trick a logged-in admin into performing unwanted actions on the site by visiting a malicious webpage.

Potential impact on your site

04Site Impact

An attacker can modify site settings or data if an admin visits a malicious link while logged in.

Conditions required to exploit

05Prerequisites

Admin must be logged in and visit an attacker-controlled webpage; no special privileges required.

Key dates

06Disclosure timeline

May 5, 2026 CVE published
May 5, 2026 Record updated

Related vulnerabilities

08Related CVE