MEDIUM CVSS 6.5
Published: 2022-02-28

CVE-2021-25081

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

CyberVault Technical Summary

Analyst Synthesis

Technical analysis, exploit verification, and patch instructions for CVE-2021-25081 impacting wpgooglemap wp_google_map. Evaluated with CVSS Base Score of 6.5 (MEDIUM).

Original NVD Description

Source: NIST NVD
The Maps Plugin using Google Maps for WordPress plugin before 1.8.4 does not have CSRF checks in most of its AJAX actions, which could allow attackers to make logged in admins delete arbitrary posts and update the plugin's settings via a CSRF attack

📊 CVSS v3.1 Metric Breakdown

Attack Vector
Network (AV:N)
Exploitable remotely across internet boundaries
Attack Complexity
Low (AC:L)
No specialized conditions required
Privileges Required
None (PR:N)
Unauthenticated execution
User Interaction
Required (UI:R)
User must click or open resource
Scope
Unchanged (S:U)
Confined to same security context
Confidentiality
None (C:N)
No data confidentiality impact
Integrity
High (I:H)
Total modification of target system
Availability
None (A:N)
No system availability impact

🎯 Affected Versions Matrix

Affected Product wpgooglemap / wp_google_map
Affected Versions *
Weakness Enumeration CWE-352

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-2021-25081 impacting wpgooglemap wp_google_map.

⚡ Nuclei Detection Template (YAML) cve-2021-25081.yaml
id: cve-2021-25081

info:
  name: wpgooglemap wp_google_map - Security Advisory & Vulnerability Scan
  author: cybervault-security-intel
  severity: medium
  description: |
    Automated signature & scanner for CVE-2021-25081 affecting wpgooglemap wp_google_map.
    Evaluation: The Maps Plugin using Google Maps for WordPress plugin before 1.8.4 does not have CSRF checks in most of its AJAX actions, which could allow attackers...
  reference:
    - https://cybervault-cve.pages.dev/cve/CVE-2021-25081
  classification:
    cvss-metrics: CVSS:3.1/CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N
    cvss-score: 6.5
    cve-id: CVE-2021-25081
    cwe-id: CWE-352
  tags: cve,cve-2021-25081,wpgooglemap,wp_google_map,medium

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

import requests
import sys

def verify_vulnerability(target_url):
    print(f"[*] Auditing {target_url} for CVE-2021-25081 (wpgooglemap wp_google_map)...")
    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 wpgooglemap wp_google_map 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-2021-25081.sh
# Recommended Remediation & Patching Commands for CVE-2021-25081
# 1. Update package via distribution package manager:
sudo apt-get update && sudo apt-get --only-upgrade install wp_google_map 2>/dev/null || \
sudo dnf upgrade wp_google_map 2>/dev/null || \
sudo yum update wp_google_map

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

# 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-2021-25081 in wpgooglemap wp_google_map?

Review vendor-specific security notices and update wpgooglemap wp_google_map 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-2021-25081?

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-2021-25081?

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

Risk Snapshot
6.5
MEDIUM SEVERITY
CVE ID CVE-2021-25081
Weakness CWE-352
Vendor wpgooglemap
Product wp_google_map
Published 2022-02-28
Vector CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N