Security readout for executives and security teams
Plain-English summary
A WordPress user with access to Add Multiple Marker could be tricked into causing an unwanted action through the plugin. The sources describe a CSRF flaw in versions up to 1.2. It is medium severity because user interaction is required and the documented impact is limited.
Executive priority
Treat as a routine medium-priority WordPress plugin remediation. Prioritize public or business-critical WordPress sites, especially where administrators frequently manage content through logged-in browser sessions.
Technical view
CVE-2022-45080 is a CWE-352 CSRF vulnerability in KrishaWeb Add Multiple Marker for WordPress <= 1.2. CVSS 3.1 is 5.4: network attack, low complexity, no attacker privileges, user interaction required, no confidentiality impact, low integrity and availability impact.
Likely exposure
Exposure is limited to WordPress sites using the KrishaWeb Add Multiple Marker plugin at version 1.2 or earlier. The bundle does not identify affected CPEs or broader products.
Exploitation context
The source bundle does not show CISA KEV listing or cite active exploitation. The CVSS vector indicates exploitation requires user interaction, consistent with CSRF risk, but no exploit details are provided.
Researcher notes
Evidence is sparse. The bundle identifies CSRF, product, version boundary <= 1.2, CVSS, CWE-352, and Patchstack reference, but not the vulnerable endpoint, nonce behavior, role requirements, or fixed release details.
Mitigation direction
- Inventory WordPress sites for the Add Multiple Marker plugin.
- Confirm whether installed versions are 1.2 or earlier.
- Check Patchstack and vendor guidance for fixed versions or official remediation.
- Disable or remove the plugin where it is not business-critical.
- Limit administrative browsing from authenticated WordPress sessions.
Validation and detection
- Review WordPress plugin inventories across production and staging sites.
- Check plugin version metadata for Add Multiple Marker.
- Confirm no affected plugin remains active after remediation.
- Document any business exception and compensating controls.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-352: User-session and phishing behavior lookup
Client-side and session-facing weaknesses should be reviewed alongside initial-access and user-execution behaviors. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2022-45080 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 5.4 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:L
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:L2.82.5Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
5.4MediumVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:L
Source materials
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Cross-Site Request Forgery (CSRF)
Cross-Site Request Forgery (CSRF) represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.