dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2023-51418

HIGH · 7.7 CVSS v3.1 Published 2024-04-17
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
83/100
Remediation priority · High
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 Joris van Montfort JVM rich text icons.This issue affects JVM rich text icons: from n/a through 1.2.6.

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 Joris van Montfort JVM rich text icons plugin versions through 1.2.6 allows unauthorized users to access certain functionality or perform actions they should not have permission to execute.

MitigationUpdate JVM rich text icons to version 1.2.6 or later and verify that proper authorization controls are enforced for all sensitive operations.

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

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify if JVM rich text icons plugin is installed
    Locate the plugin directory named 'jvm-rich-text-icons' or 'joris-van-montfort-rich-text-icons' within your CMS or application's plugin folder (commonly wp-content/plugins/ for WordPress). Check for a main plugin file containing the plugin header with the name 'JVM rich text icons'.
    Affected if The plugin directory or files exist on the server
  2. Determine the installed plugin version
    Open the main plugin PHP file and locate the version string in the plugin header comment (e.g., 'Version: 1.2.6') or check a version constant defined in the plugin code.
    Affected if The version number found is 1.2.6 or lower (the affected range is through version 1.2.6)
  3. Verify the plugin is active
    In the application admin panel, check whether the JVM rich text icons plugin is enabled. For WordPress, go to Plugins > Installed Plugins and confirm the plugin status. If using a different CMS, check the equivalent plugin management interface.
    Affected if The plugin shows as active or enabled in the system
  4. Confirm the authorization vulnerability applies
    Since this CVE describes a missing authorization flaw, test whether unauthenticated or low-privilege users can access plugin settings, icon insertion functions, or admin-related features they should not reach. Attempt to access plugin endpoints or functions without proper authentication tokens.
    Affected if Users with insufficient privileges can access plugin functionality that should require authorization

You are affected if the JVM rich text icons plugin is installed at version 1.2.6 or earlier, is currently active, and lacks proper authorization controls on sensitive operations.

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 JVM rich text icons to version 1.2.6 or later and verify that proper authorization controls are enforced for all sensitive operations.

Have this fixed Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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