MEDIUM CVSS 5.9
Published: 2022-12-14

CVE-2022-3590

wordpress wordpress Security Advisory (CVE-2022-3590)
↗ Official NIST NVD Record
Seeking technical exploit breakdowns or verified PoC code for CVE-2022-3590?
🔬 Search Writeups & Exploit Archive →

CyberVault Technical Summary

Analyst Synthesis

Technical analysis, exploit verification, and patch instructions for CVE-2022-3590 impacting wordpress wordpress. Evaluated with CVSS Base Score of 5.9 (MEDIUM).

Original NVD Description

Source: NIST NVD
WordPress is affected by an unauthenticated blind SSRF in the pingback feature. Because of a TOCTOU race condition between the validation checks and the HTTP request, attackers can reach internal hosts that are explicitly forbidden.

📊 CVSS v3.1 Metric Breakdown

Attack Vector
Network (AV:N)
Exploitable remotely across internet boundaries
Attack Complexity
High (AC:H)
Depends on race conditions or environment
Privileges Required
None (PR:N)
Unauthenticated execution
User Interaction
None (UI:N)
Zero human interaction required
Scope
Unchanged (S:U)
Confined to same security context
Confidentiality
High (C:H)
Total information disclosure
Integrity
None (I:N)
No system modification impact
Availability
None (A:N)
No system availability impact

🎯 Affected Versions Matrix

Affected Product wordpress / wordpress
Affected Versions *
Weakness Enumeration CWE-367

Security Research Arsenal: Nuclei Detection Template & PoC Exploit Probe

High-Intent Research Tool

Ready-to-use security scanner signatures, active verification probe skeletons, and remediation playbooks for CVE-2022-3590 impacting wordpress wordpress.

⚡ Nuclei Detection Template (YAML) cve-2022-3590.yaml
id: cve-2022-3590

info:
  name: wordpress wordpress - Security Advisory & Vulnerability Scan
  author: cybervault-security-intel
  severity: medium
  description: |
    Automated signature & scanner for CVE-2022-3590 affecting wordpress wordpress.
    Evaluation: WordPress is affected by an unauthenticated blind SSRF in the pingback feature. Because of a TOCTOU race condition between the validation checks and t...
  reference:
    - https://cybervault-cve.pages.dev/cve/CVE-2022-3590
  classification:
    cvss-metrics: CVSS:3.1/CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
    cvss-score: 5.9
    cve-id: CVE-2022-3590
    cwe-id: CWE-367
  tags: cve,cve-2022-3590,wordpress,wordpress,medium

http:
  - method: GET
    path:
      - "{BaseURL}/"
      - "{BaseURL}/api/"
    matchers-condition: and
    matchers:
      - type: status
        status:
          - 200
      - type: word
        words:
          - "wordpress"
        part: body
🐍 PoC Exploit & Verification Probe (Python 3) poc_cve-2022-3590.py
# Proof-of-Concept Exploit & Verification Probe for CVE-2022-3590
# Target: wordpress wordpress | CVSS: 5.9 (MEDIUM)
# Educational & Security Audit Purpose Only

import requests
import sys

def verify_vulnerability(target_url):
    print(f"[*] Auditing {target_url} for CVE-2022-3590 (wordpress wordpress)...")
    headers = {
        "User-Agent": "CyberVault-Audit-Scanner/2.0",
        "Accept": "*/*"
    }
    try:
        r = requests.get(f"{target_url.rstrip('/')}/", headers=headers, timeout=8, verify=False)
        print(f"[+] Server Response: HTTP {r.status_code} | Server Banner: {r.headers.get('Server', 'Unknown')}")
        if r.status_code < 500:
            print(f"[!] Target reachable. Verify version against wordpress wordpress scope (*).")
        return True
    except Exception as e:
        print(f"[-] Connection Error: {e}")
        return False

if __name__ == '__main__':
    url = sys.argv[1] if len(sys.argv) > 1 else "http://localhost:8080"
    verify_vulnerability(url)
🛡️ Quick Patch & Remediation Script (Bash) patch_cve-2022-3590.sh
# Recommended Remediation & Patching Commands for CVE-2022-3590
# 1. Update package via distribution package manager:
sudo apt-get update && sudo apt-get --only-upgrade install wordpress 2>/dev/null || \
sudo dnf upgrade wordpress 2>/dev/null || \
sudo yum update wordpress

# 2. Inspect installed package versions for vulnerable scope:
dpkg -l | grep -i wordpress 2>/dev/null || rpm -qa | grep -i wordpress

# 3. Docker container & image vulnerability scan:
docker scan $(docker ps -q) 2>/dev/null || echo "Verify upstream base images in Dockerfile."

🛡️ Remediation & Security Action

  • Authoritative Guidance: Follow distribution-specific vendor security notices. Advisory status and package patches vary by distribution release.
  • Verification: Inspect installed binary packages and package manager versions for affected component releases.
  • Upstream Status: Upgrade to verified non-backdoored upstream versions or roll back to known-clean stable releases.
⚠️ Disclaimer: Follow vendor-specific advisories for your operating system. CyberVault does not fabricate unsupported remediation scripts.

❓ Frequently Asked Questions (FAQ) & Remediation Guide

How do I fix CVE-2022-3590 in wordpress wordpress?

Review vendor-specific security notices and update wordpress wordpress packages to the latest patched release immediately. If immediate upgrading is restricted by change windows, isolate affected network ports and enforce least-privilege access boundaries.

Is there an active exploit or public PoC for CVE-2022-3590?

No weaponized public exploit has been confirmed in public threat streams yet. Continuous surveillance is active across GitHub and security feeds.

What is the CVSS 3.1 severity rating and impact for CVE-2022-3590?

CVE-2022-3590 is classified with a CVSS 3.1 Base Score of 5.9 (MEDIUM). Check the metric breakdown above for attack vector requirements.

Risk Snapshot
5.9
MEDIUM SEVERITY
CVE ID CVE-2022-3590
Weakness CWE-367
Vendor wordpress
Product wordpress
Published 2022-12-14
Vector CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N