dbcve.org
QubelyWordPress extension · Themeum

CVE-2025-26767

MEDIUM · 5.4 CVSS v3.1 Published 2025-02-16
Fix available
A fix is available. Upgrade to 1.8.13 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in Themeum Qubely qubely allows Stored XSS.This issue affects Qubely: from n/a through <= 1.8.12.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

Stored Cross-site Scripting (XSS) vulnerability in the Themeum Qubely WordPress plugin allows authenticated attackers to inject malicious JavaScript through unsanitized input fields. The malicious script executes when other users view pages containing the crafted content, potentially leading to session hijacking or privilege escalation.

MitigationUpdate Qubely plugin to the latest version when available. If no update exists, implement output encoding and input validation at all user input points within the plugin code, and audit existing database content for malicious scripts.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
QubelyWordPress extension
Affected:< 1.8.13

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify Qubely plugin installation and version
    In WordPress admin, go to Plugins > Installed Plugins and locate Themeum Qubely. Note the version number displayed. Alternatively, check the plugin header in /wp-content/plugins/qubely/qubely.php for the 'Version' field.
    Affected if The installed version is lower than 1.8.13 (e.g., 1.8.12, 1.8.10, etc.)
  2. Confirm plugin is active
    In WordPress admin, go to Plugins > Installed Plugins and verify that Themeum Qubely shows as 'Active' under the plugin status.
    Affected if The plugin is active and the version is below 1.8.13
  3. Identify Qubely blocks in use
    Navigate to Pages or Posts in the WordPress admin. Edit a page using the Gutenberg editor and look for Qubely-specific blocks (such as Qubely Button, Qubely Counter, Qubely Tabs, or Qubely Accordion) in the block inserter. Check published pages that use these blocks.
    Affected if Qubely blocks are present in published content and the plugin version is vulnerable
  4. Audit content for suspicious script injections
    Search the WordPress database for stored XSS payloads. Use phpMyAdmin or WP-CLI: 'wp db query "SELECT * FROM wp_posts WHERE post_content LIKE '%<script%' OR post_content LIKE '%onload=%' OR post_content LIKE '%onerror=%'"' to find potentially malicious entries.
    Affected if Any posts or pages contain unsanitized script tags, event handlers, or JavaScript URIs within Qubely block content

The environment is affected if the Qubely plugin is installed, active, and running at a version lower than 1.8.13, with Qubely blocks in use on published pages.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 1.8.13 or later
Fixed in 1.8.13
Interim mitigation

Update Qubely plugin to the latest version when available. If no update exists, implement output encoding and input validation at all user input points within the plugin code, and audit existing database content for malicious scripts.

Recommended fix High confidence

Qubely version 1.8.13

  1. Create a complete backup of your WordPress site before making any changes
  2. Navigate to WordPress Dashboard > Plugins > Installed Plugins
  3. Locate the Qubely plugin and click Update Now (or update via WordPress updates)
  4. After updating, verify the plugin version shows 1.8.13 or later in the plugins list
  5. Clear any caching mechanisms (site cache, CDN cache) to ensure the patched version is served

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Qubely Scoped from the published advisory
  • Consultation2.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,290
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,664.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-26767 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-26767 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data