Skip to main content
veriom
Menu

Explore Veriom products, resources, and account pages.

CVE-2026-109973oxilab Flipbox cross-site scripting

Low priorityMedium6.4EPSS not scored yet

CVE-2026-109973 is a cross-site scripting in oxilab Flipbox, rated medium (6.4 on CVSS 3.1).

Why this priority: Medium severity, with no exploitation signal.

Published · Updated · NVD status: Deferred

What it is

Input is written into a web page without escaping, so an attacker's script runs in the browser of anyone who views it.

How it is reached

An attacker can exploit it over the network, with an ordinary user account, and nobody has to click anything.

What an attacker gains

The direct impact is limited: partial access to data or a partial outage. In practice, this kind of flaw lets an attacker act inside a signed-in user's browser session. The damage can spread past the vulnerable component into others.

Is it being exploited?

There is no public report of exploitation yet.

What to do

  1. No fixed version is listed yet. Find every place oxilab Flipbox runs, watch the references for a fix, and plan a replacement if it is no longer supported.
  2. While there is no fix, review who holds accounts that can reach it.

Description from NVD

The Image Hover Effects Ultimate Visual Composer (Flipbox - Awesomes Flip Boxes Image Overlay) plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'flip-box-image-upload-url-01-alt' parameter in versions up to, and including, 3.1.1. This is due to the plugin saving the image-alt field through sanitize_text_field() in Inc/Style22::register_child() (and Inc/Style18, 19, 20, 25, 29) — which preserves the double-quote character — and then concatenating the stored value into a double-quoted HTML attribute in Public_Render/Style22::default_render() (and the corresponding Style18/19/20/25/29 renderers) with no esc_attr() escaping. This makes it possible for authenticated attackers, with contributor-level access and above (when an administrator has delegated the plugin's 'Who can edit' capability via the plugin Settings page, or on multisite installations where even administrators lack unfiltered_html), to inject arbitrary web scripts in pages that will execute whenever a user accesses any page containing an affected [oxilab_flip_box] shortcode or block.

What this means for your architecture.

A CVE names a product. Whether it matters depends on where that product sits in your systems: what reaches it, which trust boundary it guards and what it can reach once compromised. Veriom maps your components, their relationships and your trust boundaries from your code, cloud and delivery evidence, so you can see where a component like this sits. The radar itself does not look at your systems.

Components it touches

  • WordPress sites and their plugins. Plugins run inside the site with its database access, and many sites are public.
  • Web front ends and single-page apps. The flaw sits between a user's browser and the web application.
  • Admin consoles served to a browser. The flaw sits between a user's browser and the web application.

Trust boundaries in play

  • Authenticated network access. An account is needed, so exposure follows who can sign in: customers, partners or staff.
  • Isolation between components. The impact crosses out of the vulnerable component into others it should be isolated from.
  • Between a user's browser and the web application. An attacker who crosses it can act inside a signed-in user's browser session.

Questions to answer about your own systems

  • Where does oxilab Flipbox run in your systems, and at which version?
  • Which of those instances can be reached from the internet or partner networks?
  • What can it reach once compromised: which data stores, secrets and services?
See how Veriom maps an architectureTake the interactive tour

Read more

Sources

  • CVE records and CVSS scores from the NVD CVE API. This product uses the NVD API but is not endorsed or certified by the NVD.
  • Exploitation status from CISA’s Known Exploited Vulnerabilities catalog.
  • Exploit likelihood from FIRST’s Exploit Prediction Scoring System (EPSS), refreshed daily.
  • Explanations are written by Veriom from fixed templates over each record’s data, not by a person reviewing each CVE. Descriptions are quoted from the records as published.