Add Multiple MarkerWordPress extension · Krishaweb
CVE-2022-45080
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 KrishaWeb Add Multiple Marker plugin <= 1.2 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 confidenceCross-Site Request Forgery (CSRF) vulnerability in the KrishaWeb Add Multiple Marker WordPress plugin version 1.2 and below. The plugin fails to implement proper anti-CSRF token validation, allowing attackers to forge requests on behalf of authenticated administrators to modify marker data.
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
Add Multiple MarkerWordPress extension
<= 1.2CVSS 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 plugin installation and versionCheck the WordPress plugins directory for the 'add-multiple-marker' or 'krishaweb-add-multiple-marker' folder, and read the main plugin file header to find the Version: X.X declarationAffected if The installed version is 1.2 or lower, or if the Version header cannot be found (implying an unversioned vulnerable release)
-
Confirm plugin is activeQuery the WordPress options table for the active_plugins option, or use wp-cli: wp plugin list --status=active --name='*marker*'Affected if The plugin appears in the list of active plugins
-
Inspect admin AJAX handlers for nonce validationExamine the plugin's main PHP file(s) for AJAX action handlers (add_action calls with wp_ajax_ or wp_ajax_nopriv_ hooks). Search for the absence of check_admin_referer() or wp_verify_nonce() calls before processing requestsAffected if AJAX handlers exist that process state-changing requests (like saving marker data) without calling check_admin_referer() or wp_verify_nonce()
-
Inspect form submissions for CSRF protectionExamine the plugin's admin pages for HTML forms (typically in files under admin/ or views/). Check if forms include wp_nonce_field() or similar nonce generation functions as hidden fieldsAffected if Forms that modify marker data (add/edit/delete) lack nonce fields or token validation
-
Check frontend AJAX and public-facing endpointsReview any public-facing AJAX endpoints registered by the plugin (add_action calls with wp_ajax_nopriv_). Verify if these endpoints lack nonce verificationAffected if Public endpoints exist that can modify marker data without CSRF token validation
A user is affected if the KrishaWeb Add Multiple Marker plugin version 1.2 or lower is installed and active, and the plugin code lacks proper nonce validation on its form submissions or AJAX actions that modify marker data.
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 actions within the plugin, and verify these nonces on the server side before processing any state-changing requests.
Fix this in Add Multiple Marker
Scoped from the published advisory
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-45080 — 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-2022-45080 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