CVE-2023-46693
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 · uneditedCross Site Scripting (XSS) vulnerability in FormaLMS before 4.0.5 allows attackers to run arbitrary code via title parameters.
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 confidenceCross Site Scripting (XSS) vulnerability in FormaLMS before version 4.0.5 allows attackers to inject malicious scripts via title parameters. The vulnerability enables execution of arbitrary JavaScript code in the context of affected users' browsers, potentially leading to session hijacking, credential theft, or malicious actions on behalf of authenticated users.
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< 4.0.5CVSS 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
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/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 FormaLMS installation versionLocate the version file or check the admin dashboard for the installed FormaLMS version. Common locations include a version.php file in the root directory or the admin control panel's system information section.Affected if The installed version is lower than 4.0.5 (for example, 4.0.4, 4.0.3, or earlier releases).
-
Locate title parameter handlersSearch the codebase for files that process title-related parameters. Look for POST or GET parameters containing 'title' in form handlers and API endpoints, particularly in areas dealing with courses, modules, or content creation.Affected if The application processes title parameters from user input without visible evidence of sanitization or encoding functions in the code.
-
Check input validation configurationExamine the application's security configuration files and any middleware that handles input validation. Look for settings related to XSS protection or input filtering, typically found in security or filter configuration files.Affected if No input validation or output encoding mechanisms are configured for title parameter handling, or these protections are disabled.
-
Review authentication requirementsDetermine if the title parameter processing is accessible to authenticated users only. Check session management and access control configurations to understand the user context required to trigger the vulnerable code path.Affected if The title parameter input points are accessible to authenticated users without additional security review, allowing the XSS payload to be stored and executed.
Your environment is affected if the installed FormaLMS version is below 4.0.5 and title parameters are processed by the application without proper input validation and output encoding.
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 · scoped4.0.5
Upgrade FormaLMS to version 4.0.5 or later. If immediate patching is not possible, implement input validation and output encoding on all title parameter handlers, and consider deploying a Web Application Firewall as a temporary compensating control.
FormaLMS 4.0.5
- 1. Back up the entire FormaLMS installation directory and database before making any changes
- 2. Download FormaLMS version 4.0.5 from the official source at www.formalms.org
- 3. Follow the official upgrade instructions to update the installation to version 4.0.5
- 4. Verify the upgrade was successful by logging into the admin panel
- 5. Test that the title parameter input fields properly sanitize user input to prevent XSS
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.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,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-46693 — 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-2023-46693 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