LiveActive security incident?Get immediate response
CVE Record

CVE-2025-68894: WordPress ShoutOut plugin <= 4.0.2 - Reflected Cross Site Scripting (XSS) vulnerability

Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in shoutoutglobal ShoutOut shoutout allows Reflected XSS.This issue affects ShoutOut: from n/a through <= 4.0.2.

HighCVSS 7.1Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2025-68894 is a reflected cross-site scripting issue in the WordPress ShoutOut plugin through version 4.0.2. An attacker could trick a user into opening crafted content that runs script in the site context. Sources rate it high, but do not show known active exploitation.

Executive priority

Treat as a high-priority web application issue for sites using ShoutOut. The business risk is mainly user trust, session exposure, and site integrity. Urgency depends on whether the plugin is deployed; there is no source-backed evidence of active exploitation.

Technical view

The issue is CWE-79 improper neutralization during web page generation in shoutoutglobal ShoutOut. CVSS 3.1 is 7.1: network attack vector, low complexity, no privileges required, user interaction required, scope changed, and low confidentiality, integrity, and availability impact.

Likely exposure

Exposure is limited to WordPress sites using the ShoutOut plugin at version 4.0.2 or earlier. Sites not running this plugin are not indicated as affected by the provided sources.

Exploitation context

The CVSS vector indicates unauthenticated network reachability but requires user interaction. The provided sources do not indicate CISA KEV listing or active exploitation. No public exploit details are included in the source bundle.

Researcher notes

Evidence is limited to the CVE data and Patchstack reference. The affected data includes a version field of “0,” while the description states affected through 4.0.2. No fixed version, patch status, or exploitation-in-the-wild evidence is provided in the supplied sources.

Mitigation direction

  • Inventory WordPress sites for the ShoutOut plugin and record installed versions.
  • Check vendor, WordPress plugin, or Patchstack guidance for a fixed version or official mitigation.
  • Prioritize updating or replacing affected installations when trusted guidance becomes available.
  • If the plugin is not business-critical, consider disabling it pending vendor guidance.
  • Apply standard WordPress hardening and least-privilege admin practices.

Validation and detection

  • Confirm whether ShoutOut is installed on each WordPress site.
  • Verify whether installed versions are 4.0.2 or earlier.
  • Review the CVE and Patchstack entry for updated remediation information.
  • Check security monitoring for suspicious user-facing script execution reports.
  • Avoid production exploit testing; use vendor-safe validation only.
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-2025-68894 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-2025-68894Attack 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
shoutoutglobalShoutOutshoutout, 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.