CVE-2024-9980
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 · uneditedThe ee-class from FormosaSoft does not properly validate a specific page parameter, allowing remote attackers with regular privileges to inject arbitrary SQL commands to read, modify and delete database contents.
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 confidenceThe ee-class component from FormosaSoft contains a SQL injection vulnerability in a page parameter that is not properly validated. Attackers with standard user privileges can inject arbitrary SQL commands through this parameter, allowing them to read, modify, or delete database contents.
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<= 2024-03-26CVSS 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
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/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 Formosasoft Ee Class installationLocate the ee-class component installation directory or check software inventory for 'Formosasoft Ee Class' or 'ee-class'Affected if The product is installed and no version is found or version is <= 2024-03-26
-
Determine installed versionCheck the ee-class version information (typically found in about page, version file, or application metadata)Affected if Installed version is 2024-03-26 or earlier, or version cannot be determined (treat as vulnerable)
-
Identify the page parameter endpointLocate the web application endpoint that accepts the vulnerable 'page' parameter (check URL parameters in forms or navigation links within the ee-class application)Affected if The application uses a 'page' parameter in URLs without evidence of parameterized query implementation
-
Test for SQL injection susceptibilityUse the application's page parameter with a simple SQL injection test payload (e.g., page=1' OR '1'='1) and observe database error responses or unexpected behaviorAffected if The application returns database error messages or displays data not intended for the current user context
-
Verify database user privilegesCheck the database account used by ee-class - if it has more than read-only privileges (e.g., SELECT, INSERT, UPDATE, DELETE on multiple tables)Affected if Database user has elevated privileges beyond minimal read-only access, enabling exploitation impact
User is affected if Formosasoft Ee Class version is 2024-03-26 or earlier AND the page parameter endpoint is accessible in their deployment.
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.
From vendor dataImplement parameterized queries (prepared statements) for all database interactions involving the affected page parameter, and add proper input validation and sanitization. Apply principle of least privilege to database accounts.
- Consultation3.0 h
- Implementation6.0 h
- Testing5.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 $4,752.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-9980 — 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-2024-9980 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