dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2026-57335

MEDIUM · 6.5 CVSS v3.1 Published 2026-06-29
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable Zero-click 7 weeks old

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
Subscriber Broken Access Control in Ads by WPQuads <= 3.0.3 versions.

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

This is a Broken Access Control vulnerability in the Ads by WPQuads WordPress plugin (versions 3.0.3 and below). Users with the 'subscriber' role, which is typically the lowest privilege level in WordPress, can access administrative or privileged functionality that should be restricted to higher-privilege users like administrators.

MitigationUpdate Ads by WPQuads to the latest version, or implement proper role-based capability checks on all sensitive plugin functions to ensure subscriber-level users cannot access administrative features.

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

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
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/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 WPQuads plugin is installed
    Navigate to WordPress admin > Plugins, or inspect the /wp-content/plugins/quick-adsense-reloaded/ directory. Confirm the plugin 'Ads by WPQuads' or 'Quick Adsense Reloaded' is present.
    Affected if Plugin is installed and active
  2. Check installed plugin version
    In WordPress admin > Plugins, find WPQuads in the plugin list and note the version number displayed, or read version from the plugin's main PHP file header.
    Affected if Version is 3.0.3 or lower
  3. Confirm subscriber role users exist
    In WordPress admin > Users, review the list of users and their assigned roles. Note if any users have the 'subscriber' role assigned.
    Affected if At least one user with subscriber role exists in the system
  4. Check for unauthorized admin access via subscriber
    Log in as a subscriber-level user and attempt to access WordPress admin dashboard areas or plugin settings pages that should be restricted to administrators. Observe if access is granted when it should be denied.
    Affected if Subscriber role can access admin pages or plugin configuration settings

If WPQuads version 3.0.3 or lower is installed AND subscriber-role users exist and can access administrative functionality, the environment is affected by this CVE.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update Ads by WPQuads to the latest version, or implement proper role-based capability checks on all sensitive plugin functions to ensure subscriber-level users cannot access administrative features.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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