CVE-2025-69241
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 FirstName and LastName parameters in profile editing functionality. Authenticated attacker 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 confidenceStored XSS vulnerability in Raytha CMS allows authenticated users to inject malicious HTML/JavaScript via FirstName and LastName fields in profile editing. The injected payload persists in the database and executes when other users view the profile 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 installationLocate Raytha web application files or check web server for Raytha CMS. Look for typical installation directories or check the application banner/version endpoint if available.Affected if Raytha CMS is present in the environment and is running a version lower than 1.4.6
-
Check installed Raytha versionAccess the administration panel or check the application configuration files for the version number. The version is typically displayed in the admin dashboard footer or in a config/settings file within the Raytha installation directory.Affected if The installed version is any version prior to 1.4.6 (e.g., 1.4.5, 1.4.0, etc.)
-
Verify user profile editing is accessibleLog in as an authenticated user and navigate to the profile settings or account management section. Confirm that FirstName and LastName fields are editable.Affected if Profile editing functionality exists and users can modify their FirstName and LastName values
-
Inspect user profile data for malicious contentQuery the underlying database for user profile records. Examine the FirstName and LastName columns in the users table for any HTML tags, script tags, or unusual encoded characters that may indicate stored XSS payloads.Affected if Any user profiles contain unsanitized HTML or JavaScript in FirstName or LastName fields
A user is affected if their Raytha CMS installation is version 1.4.5 or earlier AND the profile editing feature is accessible to authenticated users, or if the database already contains malicious payloads in user name fields.
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, which contains the fix for this stored XSS vulnerability.
version 1.4.6
- 1. Back up the current Raytha CMS database and files before upgrading.
- 2. Upgrade Raytha CMS to version 1.4.6 following the official upgrade documentation at raytha.com.
- 3. After upgrading, log in to the admin panel and navigate to the profile editing functionality.
- 4. Test that the FirstName and LastName fields now properly sanitize or reject malicious input (e.g., <script>alert(1)</script>).
- 5. Clear any cached content if the application uses caching, as stale cached pages may still contain the malicious payload.
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-69241 — 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-69241 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