LiveActive security incident?Get immediate response
CVE Record

CVE-2021-36911: WordPress Comment Engine Pro plugin <= 1.0 - Stored Cross-Site Scripting (XSS) vulnerability

Stored Cross-Site Scripting (XSS) vulnerability discovered in WordPress Comment Engine Pro plugin (versions <= 1.0), could be exploited by users with Editor or higher role.

MediumCVSS 4.8Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2021-36911 is a stored cross-site scripting issue in the WordPress Comment Engine Pro plugin through version 1.0. A user with Editor or higher privileges could store malicious script content that later runs when another user views affected content. The business risk is account/session impact and page tampering, not server takeover based on the supplied sources.

Executive priority

Handle as a moderate WordPress hygiene item. Prioritize faster if the plugin is active on customer-facing sites, sites with many editors, or sites handling sensitive user sessions. No emergency active-exploitation signal is provided in the bundle.

Technical view

The vulnerability is CWE-79 stored XSS in @rex1989 Comment Engine Pro for WordPress <= 1.0. CVSS 3.1 is 4.8: network reachable, low complexity, high privileges required, user interaction required, changed scope, low confidentiality and integrity impact, no availability impact.

Likely exposure

Exposure is limited to WordPress sites running Comment Engine Pro <= 1.0. Practical risk is higher where many trusted users have Editor or higher roles, especially on public or client-facing sites. The sources do not identify the vulnerable field, affected route, or fixed version.

Exploitation context

The supplied bundle does not show CISA KEV listing or any cited evidence of active exploitation. Exploitation requires an already privileged WordPress user and someone else interacting with affected stored content, which reduces likelihood but still matters for multi-user sites.

Researcher notes

Evidence is sparse. The CVE provides the product, affected version range, role requirement, CWE, and CVSS vector, but not the vulnerable parameter, proof of concept, exploit activity, or fixed version. Validate exposure through inventory and role review rather than offensive testing.

Mitigation direction

  • Inventory WordPress sites for Comment Engine Pro and installed version.
  • Remove or disable the plugin if it is not required.
  • Check the plugin page and Patchstack entry for current vendor guidance.
  • Apply a vendor-provided update if one is available.
  • Restrict Editor or higher roles to trusted accounts only.
  • Review suspicious recent changes by privileged WordPress users.

Validation and detection

  • Confirm whether Comment Engine Pro is installed on each WordPress site.
  • Record plugin version and compare it with the affected <= 1.0 range.
  • Review WordPress users with Editor, Administrator, or equivalent privileges.
  • Check logs or content history for unexpected script-like markup.
  • Verify remediation against vendor or Patchstack guidance before closure.
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-2021-36911 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-2021-36911Attack 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
@rex1989Comment Engine Pro (WordPress plugin)<= 1.0Listed
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.