Skip to content
Noroxi
CVE-2022-30705· NVD / CVE Program· CNA Patchstack

WordPress WordPress Ping Optimizer Plugin <= 2.35.1.2.3 is vulnerable to Cross Site Request Forgery (CSRF)

Noroxi assessment

Priority: Monitor (action score 35/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.22% (FIRST EPSS).
  • Anyone who can reach it over the internet can trigger it. No account or password is required. A user must open a link or visit a page. No special conditions are required; it is repeatable.
  • Fixed version: Pankaj Jha WordPress Ping Optimizer 2.35.1.3.0.
  • Severity is disputed: the assigning authority (CNA) scores it 5.4, NVD 8.8.

Low priority for now. Upgrade to Pankaj Jha WordPress Ping Optimizer 2.35.1.3.0 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

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

HighCVSS 8.8 · v3.1—No exploit Fix available
Published
Mar 27, 2023
Updated
Jun 17, 2026
EPSS
0.2% · 12th percentile

Report tools

JSON

Action score

35

Monitor

Low priority for now.

CVSS
35 / 40 · 8.8 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.2%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
8.8
CNA · Patchstack
5.4
3.4 point gap

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

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Is WordPress Ping Optimizer on your site?

WP Lens reads your site's plugin, theme and WordPress versions from the outside and matches them to known vulnerabilities. Works without an account.

Follow CVE-2022-30705

Is WordPress Ping Optimizer on your site?

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Port scanning: 5 full scans a day (members only)
  • Uptime monitoring: 1 site, instant email when it goes down
  • Verify your domain: subdomains and takeover risk scanned every week
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for wordpress ping optimizer project records
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
wordpress ping optimizer projectwordpress ping optimizer

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • wordpress ping optimizer project wordpress ping optimizerbefore 2.35.1.3.0

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Patchstack). Independent of NVD's CPE analysis and usually ahead of it.

  • Pankaj Jha WordPress Ping Optimizer

    • n/a and later · up to and including 2.35.1.2.3affectedfixed in 2.35.1.3.0

Same product

wordpress ping optimizer project: all records

Other highest-scoring records for the same primary product.

  • CVE-2023-6385WordPress Ping Optimizer <= 2.35.1.3.0 - Log Clearing via CSRF
    17Monitor
  • CVE-2022-1591WordPress Ping Optimizer < 2.35.1.3.0 - Arbitrary Settings Update via CSRF
    17Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Pankaj Jha WordPress Ping Optimizer2.35.1.3.0Vendor (CNA)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Anyone who can reach it over the internet can trigger it.
  • No account or password is required.
  • A user must open a link or visit a page.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
high · data can be read
Integrity
high · data or configuration can be modified
Availability
high · the service can be disrupted
Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
Required
Scope
Unchanged
Confidentiality impact
High
Integrity impact
High
Availability impact
High

Weakness class (CWE)

CWE-352 · Cross-Site Request Forgery (CSRF)

CVSS vector

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

nvd-primary

Root cause

State-changing requests rely on the session cookie the browser sends automatically; nothing verifies that the request came from the user’s own page.

The bug in code

The whole CWE-352 class

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

ts
app.use(session({ cookie: { httpOnly: true } }));app.post("/account/address", updateAddress);

Fixed

ts
app.use(session({ cookie: { httpOnly: true, sameSite: "lax" } }));app.post("/account/address", csrfProtection, updateAddress);

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

ATT&CK techniques

—

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records