LiveActive security incident?Get immediate response
CVE Record

CVE-2022-30705: WordPress WordPress Ping Optimizer Plugin <= 2.35.1.2.3 is vulnerable to Cross Site Request Forgery (CSRF)

Cross-Site Request Forgery (CSRF) vulnerability in Pankaj Jha WordPress Ping Optimizer plugin <= 2.35.1.2.3 versions.

MediumCVSS 5.4Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This affects the WordPress Ping Optimizer plugin for WordPress, reported for versions up to 2.35.1.2.3. A malicious site could abuse a logged-in administrator’s browser to trigger unintended plugin actions. Expected impact is limited integrity and availability, not data theft, based on the supplied CVSS vector.

Executive priority

Treat as a moderate WordPress plugin risk. Prioritize internet-facing business sites and administrator-heavy environments, but this is below emergency priority absent evidence of active exploitation or severe impact.

Technical view

CVE-2022-30705 is a CWE-352 cross-site request forgery issue in Pankaj Jha WordPress Ping Optimizer. The CVSS 3.1 vector is AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:L, meaning network-reachable attack setup, required victim interaction, and low integrity/availability impact. Sources do not provide exploit mechanics or a named fixed version.

Likely exposure

Exposure is limited to WordPress sites with the WordPress Ping Optimizer plugin installed, especially versions at or below 2.35.1.2.3. Sites without this plugin are not indicated as affected by the provided sources.

Exploitation context

The CVE is not listed as KEV, and the supplied sources do not state active exploitation. Exploitation would require convincing a logged-in WordPress user, likely an administrator, to interact with attacker-controlled content.

Researcher notes

The source bundle identifies CSRF and CVSS impact but does not include request details, nonce behavior, exploit proof, or fixed-version confirmation. Avoid assuming broader WordPress core exposure or active exploitation without additional vendor evidence.

Mitigation direction

  • Inventory WordPress sites for the WordPress Ping Optimizer plugin.
  • Check installed plugin versions against the affected range up to 2.35.1.2.3.
  • Review vendor, WordPress plugin, or Patchstack guidance for a fixed release.
  • Disable or remove the plugin where business impact is acceptable until guidance is confirmed.
  • Restrict WordPress administrator access and reinforce anti-phishing controls.

Validation and detection

  • Confirm whether the plugin is installed and enabled on each WordPress site.
  • Record exact plugin versions and compare with the CVE affected range.
  • Review WordPress audit logs for unexpected plugin setting changes.
  • Verify update, removal, or compensating control status for affected installations.
Prepared
Confidence
medium
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-352: User-session and phishing behavior lookup

Client-side and session-facing weaknesses should be reviewed alongside initial-access and user-execution behaviors. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2022-30705 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
5.4 (3.1)
Known Exploited
No
Published

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

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
5.4CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:L2.82.5Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

5.4Medium
CVSS 3.1 vector shape for CVE-2022-30705Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
Pankaj JhaWordPress Ping Optimizerwordpress-ping-optimizer, n/aunaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-352 · source CWE mapping

Cross-Site Request Forgery (CSRF)

Cross-Site Request Forgery (CSRF) represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.