dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2022-46796

MEDIUM · 6.5 CVSS v3.1 Published 2024-12-13
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
74/100
Remediation priority · Elevated
Remotely reachable No privileges 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 VillaTheme CURCY allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects CURCY: from n/a through 2.1.25.

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 VillaTheme CURCY WordPress currency converter plugin allows attackers to exploit incorrectly configured access control security levels. The plugin fails to properly validate user capabilities before allowing access to certain functionality, potentially enabling authenticated users to perform unauthorized actions.

MitigationUpdate CURCY to the latest version when available. Until then, restrict user permissions to the minimum required roles and consider implementing additional access controls at the web server level.

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

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

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 CURCY plugin is installed
    Log into WordPress admin panel, navigate to Plugins > Installed Plugins, and search for 'CURCY' or 'VillaTheme Currency Converter'. Note whether the plugin appears in the list and whether it is activated.
    Affected if CURCY plugin is installed and activated on the WordPress site
  2. Identify installed CURCY version
    In the WordPress plugins list, locate the CURCY entry and record the version number displayed. Compare this version against the version in which the vulnerability was patched (if known).
    Affected if Installed version lacks the authorization fix and is earlier than the patched release
  3. Review user role assignments
    Navigate to Users > All Users in WordPress admin. Examine which users are assigned to roles with elevated privileges (Administrator, Editor, Author). Identify any lower-privileged users (Subscriber, Contributor) who should not have access to currency converter settings.
    Affected if Users with low-privileged roles exist who could potentially access unauthorized plugin functionality due to missing capability checks
  4. Inspect plugin capability settings
    Go to CURCY plugin settings (usually under Settings or a dedicated CURCY menu item). Check if there are options controlling who can access currency conversion features, exchange rate updates, or plugin configuration. Verify if these restrictions are properly enforced.
    Affected if Plugin settings allow authenticated users with limited roles to access functionality that should require higher privileges
  5. Test access to plugin admin functions
    Using a browser or HTTP tool, attempt to access CURCY admin pages or AJAX endpoints while logged in as a low-privileged user (e.g., Subscriber). Check if unauthorized access is granted to features like currency rate updates, API configuration, or settings changes.
    Affected if Low-privileged authenticated users can access admin-level plugin functions without proper authorization validation

A site is affected if the CURCY plugin is installed with an unpatched version and allows authenticated users with insufficient privileges to access or modify currency converter settings.

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 CURCY to the latest version when available. Until then, restrict user permissions to the minimum required roles and consider implementing additional access controls at the web server level.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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