CVE-2025-69237
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 · uneditedRaytha CMS is vulnerable to Stored XSS via FieldValues[0].Value parameter in page creation functionality. Authenticated attacker with permissions to create content can inject arbitrary HTML and JS into website, which will be rendered/executed when visiting edited page. 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 confidenceRaytha CMS versions prior to 1.4.6 contain a stored XSS vulnerability in the page creation functionality. Authenticated users with content creation permissions can inject arbitrary HTML/JavaScript payloads through the FieldValues[0].Value parameter. The malicious payload persists in the database and executes in the browsers of users who visit the affected page.
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< 1.4.6CVSS 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
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/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 checksWork through these to decide whether this CVE applies to you.
-
Identify Raytha CMS versionLocate the version file or check the admin dashboard under System > About. Common locations include version.json in the application root or the admin interface version display.Affected if The installed version is prior to 1.4.6 (e.g., 1.4.5, 1.4.4, etc.)
-
Review user roles with content creation permissionsAccess the admin panel and navigate to Users > Roles or Permissions. Identify which roles have permission to create or edit pages or content items.Affected if Any role other than highly trusted administrators has content creation or page editing permissions enabled
-
Inspect database for suspicious FieldValues entriesQuery the database table storing page or content definitions, specifically looking at the FieldValues column or JSON field where user input is stored. Search for patterns like <script, javascript:, onerror=, or other HTML/JS tags in the Value subfield.Affected if Any records contain raw HTML or JavaScript code in FieldValues[0].Value or similar user-supplied fields
-
Examine rendered pages for unencoded outputUse a browser to visit pages created by content authors. View the page source and check if user-provided content appears as raw HTML rather than HTML-encoded entities.Affected if User-supplied content renders as executable HTML/JavaScript instead of being escaped
You are affected if your Raytha CMS version is below 1.4.6 AND your database contains unsanitized content in FieldValues that renders as executable code in browsers.
Generated from the published advisory. Verify against your own configuration.
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 · scoped1.4.6
Upgrade to version 1.4.6 or later. Prior to patching, restrict content creation permissions to highly trusted users only and consider implementing additional output encoding on the frontend.
1.4.6
- Upgrade Raytha CMS to version 1.4.6 or later by following the official upgrade documentation
- After upgrade, verify the application is functioning correctly
- Confirm the FieldValues[0].Value parameter now properly sanitizes input to prevent XSS execution
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-69237 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-69237 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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