CVE-2021-25011

CVE-2021-25011 is a medium-severity vulnerability in Wpgooglemap Wp Google Map with a CVSS 3.x base score of 5.7. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-352.

Key facts

Description

The Maps Plugin using Google Maps for WordPress plugin before 1.8.1 does not have proper authorisation and CSRF in most of its AJAX actions, which could allow any authenticated users, such as subscriber to delete arbitrary posts and update the plugin's settings.

Frequently asked questions

What is CVE-2021-25011?
The Maps Plugin using Google Maps for WordPress plugin before 1.8.1 does not have proper authorisation and CSRF in most of its AJAX actions, which could allow any authenticated users, such as subscriber to delete arbitrary posts and update the plugin's settings.
How severe is CVE-2021-25011?
CVE-2021-25011 has a CVSS 3.x base score of 5.7, rated medium severity. It is exploitable over network with low attack complexity, requires low privileges and user interaction. Impact on confidentiality is none, integrity high, and availability none.
Is CVE-2021-25011 being actively exploited?
It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (34th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2021-25011?
CVE-2021-25011 affects Wpgooglemap Wp Google Map. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2021-25011?
Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.
When was CVE-2021-25011 published?
CVE-2021-25011 was published on 2022-02-28 and last updated on 2026-06-17.

References

Affected products (1)

More vulnerabilities in Wpgooglemap Wp Google Map

All CVEs affecting Wpgooglemap Wp Google Map →

Other CWE-352 (Cross-Site Request Forgery (CSRF)) vulnerabilities

Browse all CWE-352 (Cross-Site Request Forgery (CSRF)) vulnerabilities →