LiveActive security incident?Get immediate response
CVE Record

CVE-2021-38331: WP-T-Wap <= 1.13.2 Reflected Cross-Site Scripting

The WP-T-Wap WordPress plugin is vulnerable to Reflected Cross-Site Scripting via the posted parameter found in the ~/wap/writer.php file which allows attackers to inject arbitrary web scripts, in versions up to and including 1.13.2.

MediumCVSS 6.1Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2021-38331 is a reflected cross-site scripting issue in the WP-T-Wap WordPress plugin up to version 1.13.2. An attacker could trick a user into interacting with malicious input and run script in that user’s browser context. Business impact is usually account/session abuse, content tampering, or phishing, not server takeover.

Executive priority

Treat as a moderate-priority web application issue. It is not listed as known exploited in the supplied data, but exposed WordPress plugins can create user-account and brand risk. Prioritize internet-facing sites and administrative users first.

Technical view

The vulnerability is CWE-79 reflected XSS in WP-T-Wap’s wap/writer.php handling of the posted parameter. CVSS 3.1 is 6.1: network reachable, low complexity, no privileges required, user interaction required, scope changed, low confidentiality and integrity impact, no availability impact.

Likely exposure

Exposure is likely limited to WordPress sites running WP-T-Wap version 1.13.2 or earlier, especially where the plugin’s wap/writer.php path is publicly reachable. Sites not using this plugin are not implicated by the provided sources.

Exploitation context

The provided bundle does not show CISA KEV listing or active exploitation evidence. Practical exploitation requires user interaction and reflected script execution through a vulnerable parameter, so risk rises for administrator-facing workflows or trusted users likely to follow crafted links or submissions.

Researcher notes

Evidence identifies the vulnerable component and parameter but does not include exploit telemetry or detailed vendor remediation notes. Keep analysis scoped to WP-T-Wap through 1.13.2 and avoid assuming other plugins, themes, or WordPress core are affected.

Mitigation direction

  • Inventory WordPress sites for WP-T-Wap version 1.13.2 or earlier.
  • Check vendor or WordPress plugin guidance before applying a specific update path.
  • Upgrade off affected versions if a supported fixed release is available.
  • Disable or remove the plugin if no maintained fixed version is available.
  • Use WAF rules to reduce reflected XSS attempts where feasible.

Validation and detection

  • Confirm whether WP-T-Wap is installed and record the exact version.
  • Verify whether /wap/writer.php exists on exposed WordPress deployments.
  • Review access logs for unusual requests targeting /wap/writer.php.
  • Check security tooling for reflected XSS findings tied to this plugin.
  • Document affected sites, owners, and remediation decisions.
Prepared
Confidence
high
Sources
4

Public sources used

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-2021-38331 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
6.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: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
6.1CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N2.82.7Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

6.1Medium
CVSS 3.1 vector shape for CVE-2021-38331Attack 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:N

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

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
WP-T-WapWP-T-Wap1.13.2Listed
Weakness

CWE details

CWE-79

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