dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2022-42479

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

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
Missing Authorization vulnerability in TemplateHouse Soledad allows Accessing Functionality Not Properly Constrained by ACLs. This issue affects Soledad: from n/a through 8.2.5.

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

Missing Authorization vulnerability in the Soledad WordPress theme allows unauthenticated or low-privileged users to access functionality that should be protected by Access Control Lists (ACLs). The theme fails to properly enforce permission checks on certain functions or pages, enabling unauthorized access to sensitive features.

MitigationImplement proper capability checks, nonce verification, and role-based access controls on all sensitive theme functionality. Update to patched version 8.2.6 or later if available.

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
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/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. Confirm Soledad theme is installed
    In WordPress admin, go to Appearance > Themes and verify Soledad theme is active, or check /wp-content/themes/ directory for soledad folder
    Affected if Soledad theme is present and active in WordPress installation
  2. Identify installed Soledad version
    Check theme styles.css header in /wp-content/themes/soledad/style.css for 'Version:' value, or view theme in WordPress admin themes list
    Affected if Version is 8.2.5 or earlier (versions prior to 8.2.6)
  3. Check for unauthenticated access to sensitive functions
    Inspect theme PHP files in /wp-content/themes/soledad/ for AJAX handlers or functions called via wp_ajax hooks without current_user_can() capability checks
    Affected if Theme contains functionality accessible without proper capability verification
  4. Verify ACL protection on theme customizer/settings
    Access theme options panel (usually via Appearance > Customize > Soledad Options) while logged out or as a low-privileged user (subscriber)
    Affected if Able to view or modify theme settings without authentication or proper role permissions

User is affected if Soledad theme version is 8.2.5 or earlier AND the theme exposes sensitive functionality accessible to unauthenticated or low-privileged users without proper authorization checks.

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

Implement proper capability checks, nonce verification, and role-based access controls on all sensitive theme functionality. Update to patched version 8.2.6 or later if available.

Have this fixed 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 help mitigating

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-2022-42479 — 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-2022-42479 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