dbcve.org
A\+hrdApplication · Aenrich

CVE-2022-28742

HIGH · 7.5 CVSS v3.1 Published 2022-09-09
Fix available
A fix is available. Upgrade to 5.4.1125v112 / 5.5.1098v156 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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 · unedited
aEnrich eHRD Learning Management Key Performance Indicator System 5+ has Improper Access Control. The web application does not validate user session when accessing many application pages. This can allow an attacker to gain unauthenticated access to sensitive functionalities in the application

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 confidence

The aEnrich eHRD Learning Management KPI System 5+ contains Improper Access Control where the web application fails to validate user sessions on numerous application pages. This allows unauthenticated attackers to bypass authentication and access sensitive functionalities that should require valid session credentials.

MitigationImplement proper session validation and authentication checks on all application pages, particularly those containing sensitive functionality. Consider implementing centralized authentication middleware to ensure consistent session validation across the entire application.

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
A\+hrdApplication
Affected:>= 5.0, < 5.4.1125v112>= 5.5, < 5.5.1098v156>= 5.6, < 5.6.1067v110>= 6.0, < 7.0

CVSS 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
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify the installed version of aEnrich A+hrd
    Locate the version information in the application's admin panel, about page, or version file within the web root directory. Check the application header or footer which often displays the version number.
    Affected if The installed version falls within any of these ranges: >= 5.0 and < 5.4.1125v112, OR >= 5.5 and < 5.5.1098v156, OR >= 5.6 and < 5.6.1067v110, OR >= 6.0 and < 7.0
  2. Test unauthenticated access to sensitive application pages
    Attempt to access common administrative or sensitive pages (such as user management, reports, settings, or KPI dashboards) directly via URL without providing any login credentials. Use a web browser or curl to request URLs like /admin/, /user/list, /report/, /kpi/, or similar paths that should require authentication.
    Affected if The application returns a valid response with functional content instead of redirecting to a login page or returning an authentication error
  3. Verify session validation on application endpoints
    Intercept HTTP requests using a proxy tool and examine whether the application returns session-related cookies or tokens. Then remove or invalidate the session cookie and attempt to access protected resources to see if the application properly validates the session.
    Affected if The application allows access to protected pages without a valid session token or returns inconsistent authentication errors across different pages

You are affected if your installed version is in the affected ranges AND sensitive application pages are accessible without authentication credentials.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 5.4.1125v112 / 5.5.1098v156 / 5.6.1067v110 or later
Fixed in 5.4.1125v1125.5.1098v1565.6.1067v110
Interim mitigation

Implement proper session validation and authentication checks on all application pages, particularly those containing sensitive functionality. Consider implementing centralized authentication middleware to ensure consistent session validation across the entire application.

Recommended fix High confidence

A+hrd version 7.0 or later (or the equivalent patched version in your branch: 5.4.1125v112+, 5.5.1098v156+, or 5.6.1067v110+)

  1. Identify the current installed version of A+hrd eHRD Learning Management System
  2. Determine which version branch your current installation falls under (5.0-5.4.x, 5.5.x, 5.6.x, or 6.x)
  3. Obtain the appropriate fixed version from the vendor (aEnrich) - the minimum fixed versions are: 5.4.1125v112, 5.5.1098v156, 5.6.1067v110, or 7.0+
  4. Schedule a maintenance window and create a complete backup of the current system
  5. Apply the upgrade following the vendor's documented upgrade procedure
  6. Verify that the session validation is properly enforced after upgrade by testing authenticated and unauthenticated access to sensitive pages
  7. Confirm the application functions normally post-upgrade
Caveat Review vendor release notes for any functional changes or breaking changes between your current version and the target upgrade version

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in A\+hrd Scoped from the published advisory
  • Consultation4.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA3.0 h
25.0 hours of engineering $4,400
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,040.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-28742 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-28742 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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