CVE-2025-69236
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[1].Value parameter in post editing functionality. Authenticated attacker with permissions to edit posts 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 before 1.4.6 contain a stored XSS vulnerability in the post editing functionality. The FieldValues[1].Value parameter does not properly sanitize user input, allowing an authenticated attacker with post editing permissions to inject malicious HTML/JavaScript that persists and executes when other users view the edited 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.
-
Confirm Raytha CMS is installedCheck for Raytha web application files in the web root directory, or look for Raytha in the application banner/footerAffected if Raytha CMS is present in the environment
-
Identify the installed versionCheck the version number typically displayed in the application footer, admin dashboard, or in version files within the installation directoryAffected if The installed version is any version before 1.4.6 (e.g., 1.4.5, 1.4.0, etc.)
-
Verify post editing functionality is accessibleLog in to the CMS and confirm access to the post editor module - this is typically found in the Content or Posts section of the admin panelAffected if An authenticated user has post editing permissions and can access the post creation/editing interface
-
Inspect post editor parameter handlingSubmit a test post with the FieldValues[1].Value parameter containing a benign HTML tag (e.g., <img src=x onerror=alert(1)>), then view the rendered page to see if the tag executesAffected if The submitted HTML/JavaScript is rendered and executes when the post is viewed, indicating the XSS vulnerability is present
The environment is affected if Raytha CMS is installed with a version lower than 1.4.6 and the post editing feature is accessible to authenticated users.
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 Raytha CMS to version 1.4.6 or later to remediate this stored XSS vulnerability.
1.4.6
- 1. Backup your current Raytha CMS installation and database before proceeding with the upgrade.
- 2. Download Raytha version 1.4.6 from the official Raytha repository or website (raytha.com).
- 3. Follow the standard Raytha upgrade documentation to apply the update.
- 4. Verify the upgrade was successful by logging into the admin panel.
- 5. Test the post editing functionality to confirm the XSS vulnerability is no longer exploitable.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation1.0 h
- Testing1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-69236 — 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-69236 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