LiveActive security incident?Get immediate response
CVE Record

CVE-2026-27359: WordPress Awa Plugins plugin <= 1.4.4 - Reflected Cross Site Scripting (XSS) vulnerability

Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in fox-themes Awa Plugins awa-plugins allows Reflected XSS.This issue affects Awa Plugins: from n/a through <= 1.4.4.

HighCVSS 7.1Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2026-27359 is a reflected cross-site scripting issue in the WordPress Awa Plugins plugin from fox-themes, affecting versions through 1.4.4. An attacker could trick a user into opening a crafted link and run script in that user’s browser context. This is higher priority for public WordPress sites using the plugin.

Executive priority

Treat this as a near-term web risk if your organization uses Awa Plugins. It is not confirmed as actively exploited, but public WordPress XSS issues can support credential theft, session abuse, or site trust damage when users are tricked into interacting.

Technical view

The issue is CWE-79 improper input neutralization during web page generation in awa-plugins. CVSS 3.1 is 7.1, with network access, low attack complexity, no privileges required, and user interaction required. Scope is changed with low confidentiality, integrity, and availability impact. The provided data does not name a fixed version.

Likely exposure

Exposure is limited to WordPress installations with fox-themes Awa Plugins installed at version 1.4.4 or earlier. Sites not using this plugin are not affected based on the provided sources.

Exploitation context

The CVE is not listed as CISA KEV in the provided data, and no cited source confirms active exploitation. Exploitation requires user interaction, typically a victim following attacker-controlled content, but does not require attacker authentication.

Researcher notes

The record identifies reflected XSS in Awa Plugins through 1.4.4, but the supplied bundle does not include vulnerable parameters, proof-of-concept details, or a fixed version. Avoid assuming exploitation in the wild without additional evidence.

Mitigation direction

  • Inventory WordPress sites for the Awa Plugins plugin.
  • Check vendor or Patchstack guidance for a fixed version or official mitigation.
  • Update the plugin if a fixed release is available from trusted sources.
  • If no fix is available, consider disabling the plugin where business impact allows.
  • Prioritize public-facing WordPress sites and administrator-user exposure.

Validation and detection

  • Confirm whether awa-plugins is installed on each WordPress site.
  • Record installed plugin versions and flag versions 1.4.4 or earlier.
  • Review vendor and Patchstack pages for current remediation status.
  • Check web logs for unusual requests involving the plugin, without testing exploit payloads.
  • Verify any update or removal in staging before production rollout.
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-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-2026-27359 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
High
CVSS
7.1 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/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
7.1CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L2.83.7Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

7.1High
CVSS 3.1 vector shape for CVE-2026-27359Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/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
fox-themesAwa Pluginsawa-plugins, 0unaffected
Weakness

CWE details

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

CWE-79 · source CWE mapping

Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')

Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.