dbcve.org
A Blog CmsApplication · Appleple

CVE-2022-21142

CRITICAL · 9.8 CVSS v3.1 Published 2022-02-24
Fix available
A fix is available. Upgrade to 2.8.74 / 2.9.39 or later.
See remediation →
100/100
Remediation priority · Urgent
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
Authentication bypass vulnerability in a-blog cms Ver.2.8.x series versions prior to Ver.2.8.74, Ver.2.9.x series versions prior to Ver.2.9.39, Ver.2.10.x series versions prior to Ver.2.10.43, and Ver.2.11.x series versions prior to Ver.2.11.41 allows a remote unauthenticated attacker to bypass authentication under the specific condition.

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

Authentication bypass vulnerability in a-blog cms allowing remote unauthenticated attackers to bypass authentication under specific conditions. Affected versions span multiple branches: 2.8.x prior to 2.8.74, 2.9.x prior to 2.9.39, 2.10.x prior to 2.10.43, and 2.11.x prior to 2.11.41.

MitigationUpgrade a-blog cms to version 2.8.74, 2.9.39, 2.10.43, 2.11.41 or later as appropriate for the installed branch, then verify authentication mechanisms function correctly.

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 Blog CmsApplication
Affected:>= 2.8.0, < 2.8.74>= 2.9.0, < 2.9.39>= 2.10.0, < 2.10.43>= 2.11.0, < 2.11.41

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
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 checks

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

  1. Identify installed a-blog cms version
    Locate the version file or version information in the CMS installation, typically found in the admin panel or a version configuration file within the cms directory
    Affected if The installed version is 2.8.x below 2.8.74, 2.9.x below 2.9.39, 2.10.x below 2.10.43, or 2.11.x below 2.11.41
  2. Confirm admin/login endpoint accessibility
    Verify that the administrative login page is reachable from the web, typically at /admin/ or /login/ relative to the site root
    Affected if The admin interface is exposed without additional network-level restrictions or multi-factor authentication
  3. Check for publicly accessible authentication functions
    Inspect the web server configuration and CMS access controls to determine if login, password reset, or other authentication-related endpoints are exposed to unauthenticated users
    Affected if Authentication endpoints are accessible without requiring prior successful authentication or additional verification layers

A user is affected if their a-blog cms installation version is below the fixed versions (2.8.74, 2.9.39, 2.10.43, or 2.11.41) and the admin interface is accessible to unauthenticated network attackers.

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 2.8.74 / 2.9.39 / 2.10.43 or later
Fixed in 2.8.742.9.392.10.43
Interim mitigation

Upgrade a-blog cms to version 2.8.74, 2.9.39, 2.10.43, 2.11.41 or later as appropriate for the installed branch, then verify authentication mechanisms function correctly.

Recommended fix High confidence

Upgrade to a-blog cms version 2.8.74, 2.9.39, 2.10.43, or 2.11.41 (or latest available) depending on your current major version line

  1. 1. Back up the current a-blog cms installation and database before proceeding with the upgrade
  2. 2. Download the fixed version of a-blog cms (2.8.74, 2.9.39, 2.10.43, or 2.11.41 or later) from the official source at developer.a-blogcms.jp
  3. 3. Extract the new version files and replace the existing installation files
  4. 4. Update the /app.php (or /config.php) version number to match the new version
  5. 5. Clear any cached data by removing files in the /cache directory if applicable
  6. 6. Verify the upgrade was successful by logging into the admin panel
  7. 7. Confirm that the authentication bypass vulnerability is resolved by testing the specific condition mentioned in the advisory

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

Fix this in A Blog Cms Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-21142 — 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-21142 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