Winwar Medi WP Flipclock stored cross-site scripting in WordPress clock plugin
- Exploited
- No known exploitation
- Fix
- Fixed in 1.10.2
- Who is exposed
- Not reported
Summary
Winwar Medi's WP Flipclock WordPress plugin has a stored cross-site scripting flaw that lets an attacker inject malicious scripts into web pages the plugin generates. An attacker can reach it remotely over the network with low-privilege access, but a user must take an action for the attack to work.
Written by a model
Original description
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in Winwar Medi WP Flipclock wp-flipclock allows Stored XSS.This issue affects WP Flipclock: from n/a through 1.10.1.
What to do
Upgrade to a fixed version: 1.10.2.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-128894 (WordPress WP Flipclock plugin <= 1.10.1 - Cross Site Scripting (XSS) vulnerability), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-128894 (entry last updated 2026-11-20):
Affected:
- Winwar Medi WP Flipclock: fixed in 1.10.2
Fixed versions: 1.10.2.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-128894 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-128894 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://patchstack.com/database/wordpress/plugin/wp-flipclock/vulnerability/wordpress-wp-flipclock-plugin-1-10-1-cross-site-scripting-xss-vulnerability?_s_id=cve
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-128894
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-128894"}.Affected versions
- wp-flipclockfixed in 1.10.2 · through 1.10.1
cve.now Index
- Exploitation0/40No signal
- Exposure3/25Reachable over the network · Unknown: No advisory context yet
- Reach?/20Unknown. No tracked technology or package matched
- Severity6.5/10CVSS 6.5
- No patch0/5No signal
What would change the score
- Would score about 65 if added to CISA KEV
- Would score about 60 if CISA's SSVC rates exploitation active
- Would score about 29 if advisories confirm default setups are exposed
Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Evidence 3
| Kind | Source |
|---|---|
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-128894 |
| Record | NVD · CVE-2026-128894 |
| Other links 1 | |
| Link | patchstack.com · database/wordpress/plugin/wp-flipclock/vulnerability/wordpress-wp-flipclock-plugin-1-10-1-cross-site-scripting-xss-vulnerability?_s_id=cve |
Questions about CVE-2026-128894
Is CVE-2026-128894 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.
Source: cve.now feed data
Which versions are affected by CVE-2026-128894?
wp-flipclock: through 1.10.1 (fixed in 1.10.2).
Source: cve.now feed data
How do I fix CVE-2026-128894?
Upgrade to a fixed version: 1.10.2.
Source: cve.now feed data
Related
- CVE-2026-94567NukeViet CMS: Stored XSS via SVG upload: the sanitizer is blind to markup hidden inside an internal DTD entity
- CVE-2026-94565NukeViet CMS: Unauthenticated Stored XSS in the Contact module
- CVE-2026-54064NukeViet CMS: Multiple Anti-XSS Filter Bypasses Leading to Stored XSS in News Module
- CVE-2026-94598NukeViet CMS: Stored XSS via internal marker injection in iframe srcdoc sanitization
- CVE-2026-94564NukeViet CMS: Unauthenticated Stored XSS in the Contact module via HTML sanitizer bypass
- CVE-2026-129063WordPress Spectra plugin <= 2.20.5 - Cross Site Scripting (XSS) vulnerability
No corrections so far. Something wrong on this page? Report an error.