Security readout for executives and security teams
Plain-English summary
CVE-2026-22360 is a medium-severity CSRF vulnerability affecting the WordPress SearchAzon plugin from AA-Team through version 1.4. An attacker could potentially cause a victim's browser to submit an unintended request, leading to limited integrity impact. The provided sources do not show active exploitation or confirmed patch details.
Executive priority
Address during the normal vulnerability remediation cycle, with higher priority for public WordPress sites where administrators frequently remain logged in. Escalate if vendor guidance confirms broader impact or exploitation evidence emerges.
Technical view
The issue is classified as CWE-352 Cross-Site Request Forgery in the SearchAzon WordPress plugin package `searchazon`. The CVSS v3.1 score is 4.3 with vector CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N, indicating network reachability, low attack complexity, required user interaction, no confidentiality or availability impact, and low integrity impact. The title and description identify affected versions as SearchAzon <= 1.4.
Likely exposure
Exposure is likely limited to WordPress sites that have the AA-Team SearchAzon plugin installed and running at version 1.4 or earlier. Risk is higher where privileged WordPress users are likely to be logged in while browsing untrusted content, since CSRF typically depends on a victim browser submitting an unintended authenticated request.
Exploitation context
The bundle does not include KEV listing, active exploitation evidence, public exploit confirmation, or detailed exploit mechanics. User interaction is required according to the CVSS vector, and the expected impact is limited to integrity.
Researcher notes
The source bundle has a minor affected-data inconsistency: the title and description state affected versions are through <= 1.4, while the affected object lists versions as ["0"] with defaultStatus `unaffected`. This assessment relies on the title, description, CVSS, CWE, and Patchstack reference provided in the bundle. Patch evidence is not present in the bundle.
Mitigation direction
- Inventory WordPress installations for the SearchAzon plugin and confirm whether version 1.4 or earlier is installed.
- Check AA-Team, WordPress plugin repository guidance, and the Patchstack entry for an official fixed version or vendor-recommended remediation before assuming a patch version.
- If no confirmed fix is available and the plugin is not business-critical, temporarily deactivate or remove the plugin.
- Limit administrative WordPress access to trusted users and reinforce normal anti-CSRF hygiene for privileged workflows.
- Monitor for unexpected configuration or content changes related to the plugin until remediation is confirmed.
Validation and detection
- Verify the plugin slug/package `searchazon` and installed version across WordPress sites.
- Confirm whether the environment is running SearchAzon <= 1.4.
- Review vendor or Patchstack guidance for fixed-version evidence before closing the finding as remediated.
- After updating, deactivating, or removing the plugin, re-scan the WordPress installation to confirm the vulnerable version is no longer active.
- Review recent administrative activity for unexpected SearchAzon-related changes, treating this as a precaution rather than evidence of exploitation.
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-2026-22360 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
- 4.3 (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:N
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:N2.81.4Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
4.3MediumVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N
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.