Qs Dark ModeWordPress extension · Quomodosoft
CVE-2025-47628
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 · uneditedMissing Authorization vulnerability in quomodosoft QS Dark Mode qs-dark-mode allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects QS Dark Mode: from n/a through <= 3.0.
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 confidenceQS Dark Mode plugin for WordPress contains a missing authorization vulnerability allowing attackers to exploit incorrectly configured access control security levels. This is a broken access control (BAC) issue where the plugin fails to properly verify user permissions before allowing access to sensitive functionality or data. The vulnerability is exploitable by authenticated users with low privileges, potentially allowing them to access administrative functions or modify settings beyond their authorized scope.
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
Qs Dark ModeWordPress extension
<= 3.0CVSS 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
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
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 checksWork through these to decide whether this CVE applies to you.
-
Verify plugin installationNavigate to WordPress admin > Plugins and confirm 'Qs Dark Mode' or 'Quomodosoft Qs Dark Mode' is installed and activeAffected if The plugin is installed and active on the WordPress site
-
Check installed versionOpen the main plugin file (usually wp-content/plugins/qs-dark-mode/qs-dark-mode.php) and locate the Version header in the plugin comment block, or check via wp-admin > Plugins > Plugin DetailsAffected if The version number is 3.0 or lower (any version up to and including 3.0)
-
Inspect AJAX action handlers for missing capability checksExamine the plugin's main PHP file and any included PHP files for AJAX hook registrations (add_action calls with 'wp_ajax_') and verify whether each handler calls current_user_can() or a similar authorization function before executing sensitive operationsAffected if AJAX action handlers exist that do not include current_user_can() or role verification before processing requests
-
Check admin page access controlsReview the plugin code for admin menu registrations and admin_init/admin_menu hooks to identify pages or functions that handle settings or sensitive data, then verify if these include permission checksAffected if Admin functionality or settings pages lack proper role-based access control (RBAC) validation such as current_user_can('manage_options')
-
Test low-privilege user accessCreate or use a WordPress user with Subscriber role, then attempt to access known plugin AJAX endpoints or admin pages that should require elevated privileges (e.g., making POST requests to wp-admin/admin-ajax.php with plugin action names while logged in as Subscriber)Affected if A user with Subscriber-level permissions can successfully trigger plugin functions that should be restricted to administrators
A user is affected if the Quomodosoft Qs Dark Mode plugin version 3.0 or lower is installed and active, and the site allows authenticated users with low privileges (Subscriber or Contributor roles) to access administrative functions or modify settings without proper authorization checks.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor dataImplement proper authorization checks on all sensitive plugin functions and endpoints, verifying user roles and capabilities before granting access. Add role-based access control (RBAC) validation and ensure all AJAX actions and admin pages include current_user_can() checks.
Fix this in Qs Dark Mode
Scoped from the published advisory
- Consultation2.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,904.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-47628 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-47628 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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