CVE-2024-9981
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 upload a malicious PHP file first and then exploit this vulnerability to include the file, resulting in arbitrary code execution on the server.
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 confidenceThe ee-class from FormosaSoft contains a local file inclusion vulnerability where a specific page parameter is not properly validated, allowing authenticated users with regular privileges to first upload a malicious PHP file and then include it via the vulnerable parameter, resulting in arbitrary code execution on the server.
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 if ee-class is presentSearch the web application codebase for files containing 'ee-class' or 'FormosaSoft' references, typically in configuration files, headers, or class definitions.Affected if The FormosaSoft ee-class framework is found in the environment
-
Determine the installed versionLocate the version file or code that declares the ee-class version. Common locations include a version.php, config file, or the main ee-class.php file. Compare the version date against 2024-03-26.Affected if The ee-class version date is earlier than 2024-03-26 or the version cannot be determined
-
Verify the page parameter is accessibleInspect the code handling the 'page' parameter, typically in the main entry point or routing logic. Check if the parameter is used in include/require statements without sanitization.Affected if The 'page' parameter is used in dynamic includes without proper validation or path traversal checks
-
Confirm file upload functionality is enabledReview the application's upload handlers and configuration. Check if standard authenticated users can access file upload features.Affected if File upload functionality exists and is accessible to standard authenticated users without role restrictions
-
Check authentication enforcement on vulnerable endpointsExamine whether the page parameter handler and file upload endpoints properly enforce authentication and role-based access controls for standard users.Affected if Standard authenticated users can access the page parameter handler and file upload features without elevated privilege restrictions
A user is affected if the FormosaSoft ee-class version is earlier than 2024-03-26 AND the application exposes the unauthenticated/standard-user accessible page parameter with file upload functionality enabled.
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 · scoped2024-03-26
Implement strict allowlist-based validation for the page parameter to prevent path traversal and restrict file inclusion to predefined safe paths. Additionally, enforce rigorous file upload validation including file type verification, content inspection, and storage outside the web root.
Ee Class version 2024-03-26 or later
- 1. Identify the current installed version of Ee Class (FormosaSoft) by checking the application documentation or system inventory
- 2. Download the latest version of Ee Class released on or after 2024-03-26 from the official vendor (FormosaSoft) or your trusted distribution channel
- 3. Before applying the upgrade, perform a full backup of the application files, database, and configuration
- 4. Review release notes for version 2024-03-26 or later to understand changes and ensure compatibility
- 5. Deploy the upgraded version to your production environment following standard change management procedures
- 6. Verify the upgrade was successful by checking the application version and testing that the file inclusion vulnerability is no longer exploitable
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation6.0 h
- Implementation12.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 $7,680.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-9981 — 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-9981 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