LiveActive security incident?Get immediate response
CVE Record

CVE-2023-47549: WordPress EazyDocs Plugin <= 2.3.3 is vulnerable to Cross Site Scripting (XSS)

Unauth. Reflected Cross-Site Scripting (XSS) vulnerability on 302 response page in spider-themes EazyDocs plugin <= 2.3.3 versions.

MediumCVSS 6.8Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2023-47549 is a reflected XSS issue in the WordPress EazyDocs plugin through version 2.3.3. An unauthenticated attacker may be able to make script run in a victim browser through a 302 response page. The business concern is browser-session exposure, especially if administrators use affected documentation pages.

Executive priority

Address in normal vulnerability remediation cadence, faster for public WordPress sites or sites accessed by administrators. This is not critical based on the provided CVSS and exploitation evidence, but browser-session exposure can still create meaningful business risk.

Technical view

The vulnerability is CWE-79 reflected cross-site scripting in spider-themes EazyDocs for WordPress, package eazydocs, versions <= 2.3.3. CVSS 3.1 is 6.8: network reachable, no privileges, high complexity, scope changed, high confidentiality impact, no integrity or availability impact. The source names a 302 response page as the affected behavior.

Likely exposure

Exposure is limited to WordPress sites with EazyDocs installed at version 2.3.3 or earlier. Public documentation or knowledge-base pages increase practical exposure. The source bundle does not identify affected configurations beyond the plugin and version boundary.

Exploitation context

The bundle does not report active exploitation, and this CVE is not flagged as CISA KEV. Treat it as plausible web-facing risk, but do not assume mass exploitation from the provided evidence.

Researcher notes

Evidence is concise: unauthenticated reflected XSS on a 302 response page in EazyDocs <= 2.3.3. The bundle does not provide payload detail, exploit observations, or a named fixed version. Avoid assuming impact beyond confidentiality unless new vendor data confirms it.

Mitigation direction

  • Inventory WordPress sites for the EazyDocs plugin and installed version.
  • Upgrade or remediate according to vendor or Patchstack guidance.
  • Disable or remove EazyDocs where no supported fix is available.
  • Prioritize sites used by administrators or authenticated staff.
  • Monitor web-security sources for updated vendor fix details.

Validation and detection

  • Confirm whether EazyDocs is installed and version is <= 2.3.3.
  • Run an authenticated WordPress vulnerability scan that detects CVE-2023-47549.
  • Review WAF and access logs for unusual EazyDocs-related requests.
  • Verify scanner results after applying vendor-recommended remediation.
  • Document any site where the plugin remains enabled.
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-2023-47549 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.8 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:N/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
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
6.8CVSS 3.1MediumCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:N/A:N2.24Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

6.8Medium
CVSS 3.1 vector shape for CVE-2023-47549Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:N/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
spider-themesEazyDocs – Most Powerful Knowledge base, wiki, Documentation Builder Plugin (easy docs, knowledgebase)eazydocs, n/aunaffected
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.