CVE-2025-28920
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedMissing Authorization vulnerability in Jogesh Responsive Google Map responsive-google-map allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Responsive Google Map: from n/a through <= 3.1.5.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceMissing authorization vulnerability in the Jogesh Responsive Google Map WordPress plugin (versions <= 3.1.5) allows unauthenticated or unauthorized users to access functionality that should be restricted due to incorrectly configured access control security levels.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Confirm plugin installation and activation statusIn WordPress admin, go to Plugins > Installed Plugins and locate 'Jogesh Responsive Google Map' (or 'Responsive Google Map'). Check if it is installed and activated.Affected if The plugin is installed and active, indicating the vulnerable code is present in the environment.
-
Identify installed plugin versionIn the Plugins list page, click on the plugin name to view details, or inspect the plugin header in wp-content/plugins/responsive-google-map/main.php to read the 'Version' field.Affected if The installed version is 3.1.5 or lower, placing it within the vulnerable version range.
-
Check for sensitive admin functions or AJAX endpointsExamine the plugin directory (wp-content/plugins/responsive-google-map/) for PHP files containing admin_action_, wp_ajax_, or wp_ajax_nopriv_ hooks. These indicate server-side functions the plugin exposes.Affected if The plugin exposes admin or AJAX endpoints that lack capability checks (such as current_user_can() or nonce verification).
-
Verify authorization on plugin functionalityIf the plugin provides shortcodes or widgets that interact with the database or modify settings, attempt to access or trigger them while logged out or as a low-privilege user (subscriber).Affected if Unauthenticated users or lower-privileged roles can perform actions (like saving map data, modifying settings, or accessing restricted content) that should require admin-level permissions.
You are affected if the Jogesh Responsive Google Map plugin is active at version 3.1.5 or below AND exposes sensitive functions or endpoints that lack proper authorization checks, allowing unauthenticated or unauthorized users to execute restricted operations.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataImplement proper capability checks and authorization controls on all sensitive functions within the plugin; verify all user roles have appropriate permissions before executing privileged operations.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-28920 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-28920 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data