LiveActive security incident?Get immediate response
CVE Record

CVE-2022-26366: WordPress AdRotate Banner Manager Plugin <= 5.9 is vulnerable to Cross Site Request Forgery (CSRF)

Cross-Site Request Forgery (CSRF) in AdRotate Banner Manager Plugin <= 5.9 on WordPress.

MediumCVSS 5.4Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This CVE affects the WordPress AdRotate Banner Manager plugin up to version 5.9. A malicious site could cause a logged-in WordPress user to perform unintended plugin actions. Business risk is moderate because user interaction is required and the CVSS impact is limited, but exposed WordPress admin workflows should still be checked.

Executive priority

Treat as a routine but time-bounded WordPress plugin remediation item. Prioritize internet-facing business sites and administrator-heavy environments, but do not treat it as emergency exploitation without new evidence.

Technical view

CVE-2022-26366 is a CWE-352 cross-site request forgery issue in AdRotate Banner Manager for WordPress, reported as affecting versions <= 5.9. CVSS 3.1 is 5.4 with network attack vector, low complexity, no privileges, and required user interaction. The source bundle does not specify affected actions or a confirmed fixed version.

Likely exposure

Exposure is limited to WordPress sites running AdRotate Banner Manager <= 5.9. The bundle provides no CPEs and no detailed affected-version table, so confirm plugin name and version directly in WordPress inventories.

Exploitation context

The CVE is not listed as CISA KEV, and the provided sources do not state active exploitation. Exploitation would require user interaction, typically involving a logged-in WordPress user being induced to trigger an unintended request.

Researcher notes

The public bundle confirms CSRF, plugin, CVSS, CWE, and <= 5.9 wording. It does not provide request-level details, exploit status, or a named fixed version. Avoid assuming broader AdRotate products are affected.

Mitigation direction

  • Inventory WordPress sites for AdRotate Banner Manager installations.
  • Confirm whether any installed version is <= 5.9.
  • Check vendor or Patchstack guidance for the confirmed fixed release.
  • Update or remove the plugin if it is vulnerable and not required.
  • Limit WordPress admin access to trusted users.
  • Use MFA and session hygiene for WordPress administrators.

Validation and detection

  • Review WordPress plugin inventories for exact AdRotate Banner Manager versions.
  • Verify whether vulnerable installations remain enabled on public sites.
  • Check change logs for unexpected banner or plugin configuration changes.
  • Confirm remediation against vendor or Patchstack guidance.
  • Document any exception where upgrade or removal is delayed.
Prepared
Confidence
medium
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

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 · medium confidence lookup

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 lookup
cve · low confidence lookup

CVE-2022-26366 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
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

Official CVE source material

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.

1CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS vector scores

1 official score

We 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.

ScoreVersionSeverityVectorExploitImpactSource
5.4CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:L2.82.5Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

5.4Medium
CVSS 3.1 vector shape for CVE-2022-26366Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:L

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
Arnan de GansAdRotate Banner Manager (WordPress plugin)n/aunaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-352 · source CWE mapping

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.