LiveActive security incident?Get immediate response
CVE Record

CVE-2022-36282: WordPress Search Exclude plugin <= 1.2.6 - Authenticated Stored Cross-Site Scripting (XSS) vulnerability

Authenticated (editor+) Stored Cross-Site Scripting (XSS) vulnerability in Roman Pronskiy's Search Exclude plugin <= 1.2.6 at WordPress.

MediumCVSS 4.8Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This issue affects the WordPress Search Exclude plugin through version 1.2.6. A user with editor-level or higher access could store script content that later runs in another user’s browser. The business risk is moderate because exploitation requires privileged access and user interaction, but it can still affect trust, session security, and site administration.

Executive priority

Treat this as a moderate-priority WordPress hygiene issue. It is not described as actively exploited, but it affects privileged CMS workflows and could become serious if editor accounts are compromised or broadly assigned.

Technical view

CVE-2022-36282 is an authenticated stored cross-site scripting issue, classified as CWE-79, in Roman Pronskiy’s Search Exclude WordPress plugin <= 1.2.6. The CVSS 3.1 score is 4.8 with PR:H and UI:R, indicating high privileges and victim interaction are required. Impact is listed as low confidentiality and integrity impact, with no availability impact.

Likely exposure

Exposure is limited to WordPress sites running Search Exclude version 1.2.6 or earlier, especially sites where editor-level accounts are shared, numerous, weakly protected, or potentially compromised.

Exploitation context

The provided sources do not show CISA KEV listing or active exploitation evidence. Exploitation requires an authenticated editor-or-higher user and a later interaction by another user.

Researcher notes

Do not assume a fixed version from the provided bundle; only <= 1.2.6 is identified as affected. The key validation question is whether a site has the plugin installed at an affected version and whether editor-level access is controlled.

Mitigation direction

  • Identify all WordPress sites using the Search Exclude plugin.
  • Check whether installed versions are 1.2.6 or earlier.
  • Review WordPress.org and Patchstack vendor guidance for fixed-version availability.
  • Update, disable, or remove the plugin based on vendor guidance.
  • Restrict editor-level access to trusted, MFA-protected accounts.

Validation and detection

  • Confirm plugin presence and version from WordPress administration or asset inventory.
  • Review editor-or-higher accounts for unnecessary or risky access.
  • Check site content and plugin-managed fields for unexpected stored script content.
  • Monitor administrator sessions and logs for suspicious privileged activity.
  • Verify remediation by confirming the plugin is no longer on an affected version.
Prepared
Confidence
medium
Sources
4

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-79: 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-36282 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
4.8 (3.1)
Known Exploited
No
Published

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

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
3Source 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
4.8CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:L/I:L/A:N1.72.7Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

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

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

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
Roman PronskiySearch Exclude (WordPress plugin)<= 1.2.6Listed
Weakness

CWE details

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