CVE-2022-27104
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 · uneditedAn Unauthenticated time-based blind SQL injection vulnerability exists in Forma LMS prior to v.1.4.3.
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 · moderate confidenceAn unauthenticated time-based blind SQL injection vulnerability in Forma LMS versions prior to 1.4.3 allows remote attackers to inject malicious SQL queries via unspecified vectors, potentially leading to data exfiltration or complete database compromise.
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.3CVSS 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
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify Forma LMS installationCheck for the presence of Forma LMS by locating common installation paths or the 'formalms' directory name in the web server document root. Look for directories containing 'appCore', 'lib', or 'admin' folders typical of Forma LMS.Affected if Forma LMS software is present on the server
-
Locate version file or check admin panelCheck for a version file in the installation directory, commonly found as 'version.txt' or 'VERSION' in the root folder, or log into the Forma LMS admin dashboard and navigate to the About or System Info section to view the installed version.Affected if The version cannot be determined or is not visible
-
Compare installed version to vulnerable rangeCompare the discovered version number against the affected range: any version prior to 1.4.3 is vulnerable. Common format is like 1.4.2, 1.4.1, 1.4.0, etc.Affected if Installed version is less than 1.4.3 (e.g., 1.4.2, 1.4.1, 1.3.x, etc.)
-
Review web server logs for SQL injection patternsExamine access logs for the Forma LMS application for unusual time-delayed responses or SQL syntax patterns (AND, OR, UNION, SLEEP, BENCHMARK, WAITFOR) in GET or POST parameters, particularly on unauthenticated endpoints.Affected if Logs show repeated SQL-like patterns with time-based functions from external IP addresses
If Forma LMS is installed and the version is below 1.4.3, the environment is affected by this unauthenticated SQL injection vulnerability.
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.3
Upgrade Forma LMS to version 1.4.3 or later to remediate the vulnerability. If immediate upgrade is not possible, implement WAF rules to detect and block SQL injection attempts.
Forma LMS 1.4.3
- 1. Create a complete backup of the Forma LMS database and all application files
- 2. Download Forma LMS version 1.4.3 from the official Forma LMS repository (www.formalms.org)
- 3. Follow the official Forma LMS upgrade documentation to apply version 1.4.3
- 4. Verify the upgrade was successful by checking the application version
- 5. Test that the application functions correctly after the upgrade
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,888.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-27104 — 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-2022-27104 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