dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2025-23958

MEDIUM · 6.5 CVSS v3.1 Published 2025-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 →
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 FADI MED Editor Wysiwyg Background Color editor-wysiwyg-background-color allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Editor Wysiwyg Background Color: from n/a through <= 1.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 confidence

The FADI MED Editor Wysiwyg Background Color plugin (version <=1.0) lacks proper authorization checks, allowing unauthenticated or unauthorized users to exploit incorrectly configured access control security levels. This missing authorization vulnerability in the WYSIWYG editor background color component permits access to functionality that should be restricted based on user permissions.

MitigationImplement proper authorization checks and role-based access control (RBAC) to verify user permissions before allowing access to the background color editor functionality. Ensure all sensitive operations require appropriate authentication and authorization.

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. Identify if FADI MED Editor plugin is installed
    Check the installed plugins or modules in the CMS/content management system. Look for 'FADI MED Editor Wysiwyg Background Color' or similar plugin name in the plugin directory or admin interface.
    Affected if The plugin is found installed in the system
  2. Determine the installed plugin version
    Access the plugin metadata through the admin panel, plugin configuration files, or version manifest. Look for version information in the plugin's main file, readme, or package.json.
    Affected if The installed version is 1.0 or lower (any version <=1.0)
  3. Verify access control configuration for the background color feature
    Examine the plugin's access control settings, role permissions, or capability configuration files. Check if the background color editor functionality has defined permission levels or role restrictions.
    Affected if No role-based access restrictions are defined, or the feature is accessible to unauthenticated users, or 'guest' or 'anonymous' roles have access to the background color editor functionality
  4. Test unauthenticated access to the background color editor
    Use a web proxy or curl to send a request to the background color editor endpoint (typically found in plugin routes like /wysiwyg/background-color, /editor/bg-color, or similar) without providing authentication credentials.
    Affected if The request succeeds and returns a valid response instead of requiring authentication or returning an authorization error
  5. Check for missing authorization logic in plugin code
    Review the plugin source code for authorization checks before the background color save/update functions. Look for capability checks, role verification, or permission validation at the start of these functions.
    Affected if The background color save/update functions lack authorization checks or permission validation at the function entry point

A user is affected if the FADI MED Editor Wysiwyg Background Color plugin (version 1.0 or lower) is installed AND the background color editor functionality is accessible to unauthenticated users or users without proper role permissions.

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 authorization checks and role-based access control (RBAC) to verify user permissions before allowing access to the background color editor functionality. Ensure all sensitive operations require appropriate authentication and authorization.

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-2025-23958 — 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-2025-23958 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