dbcve.org
Wordpress Ping OptimizerWordPress extension · Wordpress Ping Optimizer Project

CVE-2022-30705

HIGH · 8.8 CVSS v3.1 Published 2023-03-27
Fix available
A fix is available. Upgrade to 2.35.1.3.0 or later.
See remediation →
95/100
Remediation priority · Urgent
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
Cross-Site Request Forgery (CSRF) vulnerability in Pankaj Jha WordPress Ping Optimizer plugin <= 2.35.1.2.3 versions.

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

Cross-Site Request Forgery (CSRF) vulnerability in the WordPress Ping Optimizer plugin allows attackers to trick authenticated administrators into submitting unintended requests (such as modifying plugin settings or triggering ping operations) by luring them to visit malicious pages while logged in.

MitigationUpdate the WordPress Ping Optimizer plugin to version 2.35.1.2.4 or later, which implements proper anti-CSRF tokens (nonces) for all state-changing operations.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Wordpress Ping OptimizerWordPress extension
Affected:< 2.35.1.3.0

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
High
Integrity
High
Availability
High

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

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 WordPress installation exists
    Check for the presence of wp-load.php or other WordPress core files in the web root directory
    Affected if WordPress is not present - the plugin cannot be exploited
  2. Confirm WordPress Ping Optimizer plugin is installed
    Navigate to WordPress admin dashboard under Plugins > Installed Plugins and look for 'WordPress Ping Optimizer' or check for the plugin directory in wp-content/plugins/
    Affected if The plugin is not installed - not affected
  3. Check the installed plugin version
    In WordPress admin, go to Plugins > Installed Plugins and click on the plugin to view its version details, or inspect the main plugin file (often chp_xi1s1.php or similar) for the 'Version' header comment
    Affected if Version is 2.35.1.3.0 or higher - the fix is in place; if version is less than 2.35.1.3.0, the vulnerability is present
  4. Verify plugin is active on the site
    Check the Plugins page in WordPress admin to confirm WordPress Ping Optimizer shows as 'Active'
    Affected if Plugin is not active - the CSRF attack surface does not exist currently
  5. Inspect plugin code for nonce implementation
    Access plugin files via file manager or FTP, open the main plugin PHP file, and search for 'wp_nonce_field' or 'check_admin_referer' function calls around settings update code
    Affected if No nonce verification is found in settings-handling code - the CSRF protection is missing

A site is affected if it runs WordPress with WordPress Ping Optimizer plugin versions below 2.35.1.3.0 and the plugin is active, allowing unauthenticated attackers to trick logged-in administrators into performing unintended actions.

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
Upgrade available Upgrade to 2.35.1.3.0 or later
Fixed in 2.35.1.3.0
Interim mitigation

Update the WordPress Ping Optimizer plugin to version 2.35.1.2.4 or later, which implements proper anti-CSRF tokens (nonces) for all state-changing operations.

Recommended fix High confidence

WordPress Ping Optimizer version 2.35.1.3.0

  1. Backup your WordPress site before making any changes
  2. Navigate to Plugins > Installed Plugins in WordPress admin dashboard
  3. Find WordPress Ping Optimizer in the plugin list
  4. Click 'Update now' if an update is available, or manually upload version 2.35.1.3.0 or later
  5. Verify the plugin updated successfully to version 2.35.1.3.0 or higher

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

Fix this in Wordpress Ping Optimizer 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 the upgrade done

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-2022-30705 — 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-2022-30705 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