Open Street MapWordPress extension · Info D 74
CVE-2023-45645
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 · uneditedCross-Site Request Forgery (CSRF) vulnerability in InfoD74 WP Open Street Map plugin <= 1.25 versions.
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 confidenceA Cross-Site Request Forgery (CSRF) vulnerability exists in the InfoD74 WP Open Street Map WordPress plugin versions 1.25 and below. The flaw allows attackers to induce authenticated administrators to perform unintended administrative actions by tricking them into visiting malicious sites, leveraging the lack of proper CSRF token validation on plugin actions.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
Open Street MapWordPress extension
<= 1.25CVSS 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
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
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.
-
Verify if the InfoD74 WP Open Street Map plugin is installedIn the WordPress admin dashboard, navigate to Plugins > Installed Plugins and look for 'Info D 74 Open Street Map' or check the /wp-content/plugins/ directory for a folder named similarly (e.g., 'info-d-74-open-street-map' or containing 'openstreetmap').Affected if The plugin is present in the installation
-
Confirm the installed plugin versionIn WordPress admin, go to Plugins > Installed Plugins, find the InfoD74 Open Street Map plugin, and read the version number displayed below the plugin name. Alternatively, open the main plugin PHP file (usually info-d-74-open-street-map.php) and look for the 'Version' header in the plugin comment block.Affected if The version number is 1.25 or lower
-
Identify if any administrative actions are exposedExamine the plugin directory for PHP files handling form submissions or AJAX endpoints (commonly in files with 'admin', 'ajax', 'form', or 'action' in the name). Look for WordPress admin action hooks (like admin_post_*, wp_ajax_*) that process state-changing requests without nonces.Affected if The plugin processes admin actions or AJAX requests without verifying WordPress nonces (e.g., missing check_admin_referer() or wp_verify_nonce() calls)
-
Test for CSRF protection on plugin endpointsUsing browser developer tools or a tool like Burp Suite, capture a legitimate plugin form submission or AJAX request, then replay it without the nonce parameter or with an invalid nonce to see if the action still executes.Affected if The request succeeds without a valid nonce, confirming the CSRF protection is missing or insufficient
If the InfoD74 WP Open Street Map plugin is installed at version 1.25 or below and processes administrative actions without validating WordPress nonces, the environment is affected by this CSRF vulnerability.
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 WordPress nonces (anti-CSRF tokens) on all form submissions and AJAX endpoints within the plugin, and verify the nonce validity server-side before processing any state-changing requests.
Fix this in Open Street Map
Scoped from the published advisory
- 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-2023-45645 — 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-2023-45645 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