LiveActive security incident?Get immediate response
CVE Record

CVE-2015-10095: woo-popup Plugin class-woo-popup-admin.php cross site scripting

A vulnerability classified as problematic has been found in woo-popup Plugin up to 1.2.2 on WordPress. This affects an unknown part of the file admin/class-woo-popup-admin.php. The manipulation leads to cross site scripting. It is possible to initiate the attack remotely. Upgrading to version 1.3.0 is able to address this issue. The patch is named 7c76ac78f3e16015991b612ff4fa616af4ce9292. It is recommended to upgrade the affected component. The associated identifier of this vulnerability is VDB-222327.

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

Security readout for executives and security teams

Plain-English summary

CVE-2015-10095 is a cross-site scripting issue in the WordPress woo-popup plugin versions 1.2.0 through 1.2.2. An authenticated remote user could manipulate plugin admin behavior to affect page integrity. The cited sources name version 1.3.0 as the fix.

Executive priority

Treat this as a moderate-priority WordPress hygiene issue. It is not described as actively exploited, but affected plugin versions should be upgraded because authenticated XSS can damage site integrity and trust.

Technical view

The issue is CWE-79 in admin/class-woo-popup-admin.php. CVSS v2 is 4.0 with network access, low complexity, authenticated access required, no confidentiality or availability impact, and partial integrity impact. The patch is commit 7c76ac78f3e16015991b612ff4fa616af4ce9292, released as woo-popup 1.3.0.

Likely exposure

Exposure is limited to WordPress sites using woo-popup plugin versions 1.2.0, 1.2.1, or 1.2.2. The CVSS vector indicates attacker authentication is required, reducing broad internet-scale risk but still relevant for sites with multiple admin users.

Exploitation context

The bundle supports remote, authenticated exploitation potential but does not cite active exploitation. The CVE is not listed as KEV in the provided data. No exploit steps or weaponized details are included in the source bundle.

Researcher notes

Key evidence gaps remain: the vulnerable parameter or code path is not identified in the bundle, and exploit status is not proven. Validation should focus on plugin version, patch presence, and whether untrusted users have authenticated WordPress access.

Mitigation direction

  • Upgrade woo-popup to version 1.3.0 where the plugin is required.
  • Confirm the patch commit 7c76ac78f3e16015991b612ff4fa616af4ce9292 is present.
  • Check project or vendor guidance before using alternative controls.
  • Prioritize systems with many WordPress users or delegated admin access.

Validation and detection

  • Inventory WordPress sites for the woo-popup plugin.
  • Verify installed woo-popup versions are not 1.2.0, 1.2.1, or 1.2.2.
  • Review plugin files or deployment records for the named patch commit.
  • Confirm WordPress admin access is limited to trusted accounts.
Prepared
Confidence
high
Sources
6

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-2015-10095 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 (2.0)
Known Exploited
No
Published

Vector: AV:N/AC:L/Au:S/C:N/I:P/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
5Source 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
4CVSS 2.0MediumAV:N/AC:L/Au:S/C:N/I:P/A:N82.9Primary CVE score

Vulnerability scoring details

Base CVSS 2.0 score

4Medium
CVSS 2.0 vector shape for CVE-2015-10095Access VectorAccess ComplexityAuthenticationConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: AV:N/AC:L/Au:S/C:N/I:P/A:N

Access Vector
NetworkAdjacentLocal
Access Complexity
LowMediumHigh
Authentication
NoneSingleMultiple
Confidentiality Impact
CompletePartialNone
Integrity Impact
CompletePartialNone
Availability Impact
CompletePartialNone

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/awoo-popup Plugin1.2.0, 1.2.1, 1.2.2Listed
Weakness

CWE details

CWE-79

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