dbcve.org
Watu QuizWordPress extension · Kibokolabs

CVE-2025-30844

MEDIUM · 6.1 CVSS v3.1 Published 2025-04-01
Fix available
A fix is available. Upgrade to 3.4.3 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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 Bob Watu Quiz watu allows Reflected XSS.This issue affects Watu Quiz: from n/a through <= 3.4.2.

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

A reflected cross-site scripting (XSS) vulnerability exists in Watu Quiz plugin versions up to 3.4.2. The vulnerability allows attackers to inject malicious scripts through unsanitized input that gets reflected back in the web page response without proper output encoding.

MitigationUpgrade Watu Quiz to the latest version which contains the patched code. Additionally, implement proper input validation and output encoding on all user-supplied parameters.

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
Watu QuizWordPress extension
Affected:< 3.4.3

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
None
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/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 Watu Quiz plugin is installed
    Check your WordPress plugins directory for the Watu Quiz plugin folder, or look for Watu Quiz in the WordPress admin Plugins list
    Affected if The plugin is present in the installation
  2. Determine installed plugin version
    Access the plugin file (typically the main PHP file in the watu plugin directory) and locate the Version header in the plugin comment block, or check the plugin row in WordPress admin Plugins page
    Affected if The reported version is below 3.4.3 (for example, 3.4.2, 3.4.1, 3.4.0, or any version number less than 3.4.3)
  3. Confirm the plugin is active
    Check if the Watu Quiz plugin is enabled in WordPress admin under Plugins > Installed Plugins
    Affected if The plugin is active and accessible to users
  4. Identify if user input parameters are reflected in responses
    Review quiz pages and forms that accept user input (such as quiz titles, answer fields, or URL parameters) and check if those values appear in the page HTML output without visible encoding
    Affected if User-supplied input is reflected in the page output without proper encoding (this indicates the vulnerability condition exists)

If the Watu Quiz plugin version is 3.4.2 or lower and the plugin is active with user input being reflected in pages, the environment is affected by this reflected XSS vulnerability.

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 3.4.3 or later
Fixed in 3.4.3
Interim mitigation

Upgrade Watu Quiz to the latest version which contains the patched code. Additionally, implement proper input validation and output encoding on all user-supplied parameters.

Recommended fix Moderate confidence

Watu Quiz version 3.4.3

  1. Backup your WordPress database and files before making any changes
  2. Navigate to Plugins > Installed Plugins in your WordPress admin dashboard
  3. Find 'Watu Quiz' in the plugin list
  4. Click 'Update now' if an update is available, or manually download version 3.4.3 from the WordPress plugin repository and upload it
  5. Verify the plugin version shows 3.4.3 after updating
  6. Clear any site caches if you use caching plugins

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

Fix this in Watu Quiz Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-30844 — 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-30844 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