dbcve.org
A Blog CmsApplication · Appleple

CVE-2022-23916

MEDIUM · 6.1 CVSS v3.1 Published 2022-02-24
Fix available
A fix is available. Upgrade to 2.8.75 / 2.9.40 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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
Cross-site scripting vulnerability in a-blog cms Ver.2.8.x series versions prior to Ver.2.8.75, Ver.2.9.x series versions prior to Ver.2.9.40, Ver.2.10.x series versions prior to Ver.2.10.44, Ver.2.11.x series versions prior to Ver.2.11.42, and Ver.3.0.x series versions prior to Ver.3.0.1 allows a remote authenticated attacker to inject an arbitrary script via unspecified vectors. This vulnerability is different from CVE-2022-24374.

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

Cross-site scripting (XSS) vulnerability in a-blog cms allows an authenticated remote attacker to inject arbitrary JavaScript code. The vulnerability affects multiple version series (2.8.x through 3.0.x) prior to their respective patched releases (2.8.75, 2.9.40, 2.10.44, 2.11.42, and 3.0.1). This is a stored XSS vulnerability distinct from CVE-2022-24374.

MitigationUpgrade a-blog cms to the fixed versions (2.8.75, 2.9.40, 2.10.44, 2.11.42, or 3.0.1 or later) to remediate the vulnerability. As this requires authenticated access, ensure that user account security is enforced and consider reviewing user permissions.

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.75>= 2.9.0, < 2.9.40>= 2.10.0, < 2.10.44>= 2.11.0, < 2.11.42= 3.0.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
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/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. Determine installed a-blog cms version
    Locate the version file in the a-blog cms installation directory or access the admin panel and look for the version information typically displayed in the system settings or footer area
    Affected if The version is 2.8.0 to 2.8.74, 2.9.0 to 2.9.39, 2.10.0 to 2.10.43, 2.11.0 to 2.11.41, or exactly 3.0.0
  2. Verify admin/user authentication is enabled
    Confirm that user accounts exist and authentication is configured for the a-blog cms installation
    Affected if The system allows authenticated user logins, as this XSS requires an authenticated attacker to inject the malicious script
  3. Identify if comment or user-submitted content modules are active
    Review the site configuration or installed modules in the admin panel to determine if any user input fields (such as comment forms, contact forms, or user profile fields) are enabled
    Affected if Modules that accept and store user-submitted content are enabled and accessible to authenticated users, as this is a stored XSS vulnerability

You are affected if your a-blog cms version falls within the affected ranges AND authenticated users can submit content that gets stored on the site.

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.75 / 2.9.40 / 2.10.44 or later
Fixed in 2.8.752.9.402.10.44
Interim mitigation

Upgrade a-blog cms to the fixed versions (2.8.75, 2.9.40, 2.10.44, 2.11.42, or 3.0.1 or later) to remediate the vulnerability. As this requires authenticated access, ensure that user account security is enforced and consider reviewing user permissions.

Recommended fix High confidence

Upgrade to Ver.2.8.75+, Ver.2.9.40+, Ver.2.10.44+, Ver.2.11.42+, or Ver.3.0.1+ (any branch that fits your deployment)

  1. 1. Back up the entire a-blog cms installation including database before attempting any upgrade
  2. 2. Download the appropriate fixed version from the official a-blog cms website (developer.a-blogcms.jp) or official distribution channels
  3. 3. For 2.8.x branch: upgrade to Ver.2.8.75 or later
  4. 4. For 2.9.x branch: upgrade to Ver.2.9.40 or later
  5. 5. For 2.10.x branch: upgrade to Ver.2.10.44 or later
  6. 6. For 2.11.x branch: upgrade to Ver.2.11.42 or later
  7. 7. For 3.0.x branch: upgrade to Ver.3.0.1 or later
  8. 8. Follow the official upgrade documentation for your specific version upgrade path
Caveat Minor version upgrades typically have minimal breaking changes; review release notes for your specific upgrade path for any template or configuration changes

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
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,720
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,752.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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