CVE-2022-47132
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 Cross-Site Request Forgery (CSRF) in Academy LMS before v5.10 allows attackers to arbitrarily add Administrator users.
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 confidenceThis is a Cross-Site Request Forgery (CSRF) vulnerability in Academy LMS versions prior to 5.10. An unauthenticated attacker can trick a logged-in administrator into unknowingly submitting a request that creates a new Administrator user account, effectively granting the attacker administrative access to the LMS platform.
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< 5.10CVSS 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
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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.
-
Locate Academy LMS installationSearch your web server for Academy LMS files, typically found in the web root directory. Look for files named 'academy' or folders containing 'academy' in the document root.Affected if Academy LMS is present on the server
-
Identify installed Academy LMS versionCheck the version file or system information within the LMS admin panel, typically found under 'System Settings' or 'About' in the admin dashboard. Alternatively, check the main configuration file for a version number.Affected if The installed version is below 5.10 (e.g., 5.9, 5.8, etc.)
-
Verify admin creation functionality existsLog in as an administrator and navigate to the user management or admin management section where new admin accounts can be created.Affected if The admin user creation feature is accessible and functional in the LMS
-
Check for CSRF token implementation in admin formsInspect the HTML source code of admin forms (such as the 'Add Admin' or 'Create User' page) by viewing the page source in a browser. Look for a hidden input field named 'csrf_token', 'csrftoken', or similar, or check if the form submission includes a token parameter.Affected if No CSRF token field is present in admin state-changing forms (e.g., user creation, admin account creation)
A user is affected if Academy LMS is installed with a version lower than 5.10 and the admin user creation form lacks CSRF token protection.
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 · scoped5.10
Upgrade to Academy LMS version 5.10 or later, which should contain CSRF token validation for state-changing operations. Additionally, implement SameSite cookie attributes and ensure all admin actions validate anti-CSRF tokens.
Academy LMS v5.10
- 1. Back up the current Academy LMS database and files
- 2. Download Academy LMS version 5.10 from the official source (codecanyon.net or the vendor's website)
- 3. Extract the upgrade package
- 4. Upload the new files to the server, overwriting the existing installation
- 5. Run any database migration scripts included in the upgrade
- 6. Verify the installation by logging in and checking the admin functionality
- 7. Confirm the CSRF protection is now in place by verifying admin user creation requires proper token validation
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.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,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-47132 — 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-47132 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