CVE-2022-1287
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 · uneditedA vulnerability classified as critical was found in School Club Application System 1.0. This vulnerability affects a request to the file /scas/classes/Users.php?f=save_user. The manipulation with a POST request leads to privilege escalation. The attack can be initiated remotely and does not require authentication. The exploit has been disclosed to the public and may be used.
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 confidenceA critical privilege escalation vulnerability exists in the School Club Application System 1.0 at the /scas/classes/Users.php?f=save_user endpoint. The save_user function lacks proper authentication and authorization checks, allowing unauthenticated remote attackers to create administrative accounts or escalate privileges by sending crafted POST requests.
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.0CVSS 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.
-
Confirm School Club Application System installationSearch for the presence of the /scas/ directory or the Users.php file in your web root. Common paths include /var/www/html/scas/classes/Users.php or C:\inetpub\wwwroot\scas\classes\Users.phpAffected if The file /scas/classes/Users.php exists on the server
-
Identify installed versionCheck for a version file, README, or the main index page of the application. Look for version strings like '1.0' in source code comments or configuration files within the /scas/ directoryAffected if The application version is 1.0 exactly
-
Verify vulnerable endpoint is accessibleAttempt a HEAD or GET request to http://[target]/scas/classes/Users.php?f=save_user or check your web server access logs for requests to this endpointAffected if The endpoint responds or requests to it are logged
-
Check if authentication is enforced on save_userReview the Users.php source code around the save_user function. Look for session checks, authentication includes, or role verification at the beginning of the functionAffected if No authentication or authorization check is present before the user creation logic
-
Test endpoint behaviorSend a crafted POST request to the endpoint with user creation parameters (e.g., username, password, role=admin) from an unauthenticated context and observe if the user is created successfullyAffected if An administrative account can be created without providing valid credentials
If the School Club Application System version 1.0 is installed and the /scas/classes/Users.php?f=save_user endpoint is accessible without authentication, the environment is affected by this CVE.
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 proper authentication requirements and role-based authorization checks in the save_user function to verify the requester's identity and permissions before allowing user creation or modification. Additionally, validate and sanitize all user input parameters.
- Consultation3.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-1287 — 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-1287 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