dbcve.org
RaythaApplication

CVE-2025-15540

HIGH · 8.8 CVSS v3.1 Published 2026-03-16
Fix available
A fix is available. Upgrade to 1.4.6 or later.
See remediation →
94/100
Remediation priority · Urgent
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
"Functions" module in Raytha CMS allows privileged users to write custom code to add functionality to application. Due to a lack of sandboxing or access restrictions, JavaScript code executed through Raytha’s “functions” feature can instantiate .NET components and perform arbitrary operations within the application’s hosting environment. This issue was fixed in version 1.4.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 · high confidence

Raytha CMS versions prior to 1.4.6 contain a critical privilege escalation vulnerability in the Functions module where the lack of sandboxing allows authenticated privileged users to execute arbitrary .NET operations through custom JavaScript code, effectively achieving code execution within the application hosting environment.

MitigationUpgrade Raytha CMS to version 1.4.6 or later. If the Functions module is not required, disable it to reduce attack surface.

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

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
RaythaApplication
Affected:< 1.4.6

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
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/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 Raytha CMS installation version
    Locate the version information for your Raytha CMS installation, typically found in the admin dashboard under System settings, or by inspecting the application binaries/config files for the version string
    Affected if The installed version is any release prior to 1.4.6 (for example, 1.4.5, 1.4.0, or earlier)
  2. Locate the Functions module
    Access the Raytha CMS admin panel and navigate to the Modules or Functions section to identify if the Functions module is present and enabled
    Affected if The Functions module is installed and enabled in the application
  3. Verify user access to Functions feature
    Review the user roles and permissions configuration in the admin panel to determine which user roles have access to creating or editing custom functions
    Affected if Any user account with privileged access (administrator or elevated permissions) can access the Functions module functionality
  4. Inspect function execution capabilities
    Check the configuration or code of the Functions module to confirm whether custom JavaScript or code can be written and executed directly by users
    Affected if The Functions module allows authenticated privileged users to write and execute custom code operations without sandboxing restrictions

You are affected if your Raytha CMS version is below 1.4.6 AND the Functions module is enabled with privileged user access to create or edit custom functions, as this combination allows unauthenticated or low-privilege escalation to code execution.

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.

dbcve · scoped
Upgrade available Upgrade to 1.4.6 or later
Fixed in 1.4.6
Interim mitigation

Upgrade Raytha CMS to version 1.4.6 or later. If the Functions module is not required, disable it to reduce attack surface.

Recommended fix High confidence

1.4.6

  1. Backup your current Raytha CMS database and files before proceeding with the upgrade
  2. Download Raytha CMS version 1.4.6 from the official Raytha repository or release channel
  3. Review the official upgrade instructions provided in the Raytha 1.4.6 release notes
  4. Apply the upgrade to your production environment following standard upgrade procedures
  5. Verify that the 'Functions' module now properly sandboxes or restricts access to .NET components
  6. Confirm that custom JavaScript code in the Functions feature can no longer instantiate arbitrary .NET components

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Raytha Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing4.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,900
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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