dbcve.org
A Blog CmsApplication · Appleple

CVE-2024-23183

MEDIUM · 5.4 CVSS v3.1 Published 2024-01-23
Fix available
A fix is available. Upgrade to 2.10.50 / 2.11.58 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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.3.1.x series versions prior to Ver.3.1.7, Ver.3.0.x series versions prior to Ver.3.0.29, Ver.2.11.x series versions prior to Ver.2.11.58, Ver.2.10.x series versions prior to Ver.2.10.50, and Ver.2.9.0 and earlier allows a remote authenticated attacker to execute an arbitrary script on the logged-in user's web browser.

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 confidence

A stored Cross-Site Scripting (XSS) vulnerability in a-blog cms allows an authenticated remote attacker to inject malicious JavaScript code that executes in the browsers of logged-in users when they view content containing the injected payload.

MitigationUpgrade a-blog cms to one of the patched versions: Ver.3.1.7, Ver.3.0.29, Ver.2.11.58, Ver.2.10.50 or later. Alternatively, apply vendor-supplied patches if available for unsupported versions.

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.9.0>= 2.10.0, < 2.10.50>= 2.11.0, < 2.11.58>= 3.0.0, < 3.0.29>= 3.1.0, < 3.1.7

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
Low
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/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. Locate the installed a-blog cms version
    Check the admin dashboard footer, the config file (typically config.php or version.php in the installation directory), or the system information page in the admin panel
    Affected if The version number cannot be determined or is not visible for comparison
  2. Compare your version against the affected ranges
    Review the detected version against: <= 2.9.0, >= 2.10.0 and < 2.10.50, >= 2.11.0 and < 2.11.58, >= 3.0.0 and < 3.0.29, >= 3.1.0 and < 3.1.7
    Affected if Your installed version falls within any of these vulnerable ranges: 2.9.0 or lower, 2.10.0 to 2.10.49, 2.11.0 to 2.11.57, 3.0.0 to 3.0.28, or 3.1.0 to 3.1.6
  3. Identify if user-submitted content features are active
    Check the admin panel for enabled features such as blog comments, user registrations, entry submissions, or any module that allows authenticated users to create or modify content
    Affected if Content creation or submission features are enabled and accessible to users beyond the administrator account

You are affected if your a-blog cms version is within the vulnerable ranges listed and your site allows authenticated users to submit or modify content that can be viewed by other logged-in users.

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.10.50 / 2.11.58 / 3.0.29 or later
Fixed in 2.10.502.11.583.0.29
Interim mitigation

Upgrade a-blog cms to one of the patched versions: Ver.3.1.7, Ver.3.0.29, Ver.2.11.58, Ver.2.10.50 or later. Alternatively, apply vendor-supplied patches if available for unsupported versions.

Recommended fix High confidence

Upgrade to: Ver.3.1.7 (for 3.1.x branch), Ver.3.0.29 (for 3.0.x branch), Ver.2.11.58 (for 2.11.x branch), Ver.2.10.50 (for 2.10.x branch), or Ver.2.10.50+ (for 2.9.x and earlier)

  1. 1. Identify the currently installed a-blog cms version by checking the admin panel or version file.
  2. 2. Determine which version branch you are on (2.9.x, 2.10.x, 2.11.x, 3.0.x, or 3.1.x).
  3. 3. Download the appropriate fixed version from the official a-blog cms website (developer.a-blogcms.jp) or your licensed download source.
  4. 4. Back up the current site files and database before upgrading.
  5. 5. Upload and install the fixed version: for 2.9.x and earlier upgrade to 2.10.50 or later; for 2.10.x upgrade to 2.10.50; for 2.11.x upgrade to 2.11.58; for 3.0.x upgrade to 3.0.29; for 3.1.x upgrade to 3.1.7.
  6. 6. Verify the installation was successful and test that the application functions correctly.
  7. 7. Confirm the version number is correctly displayed in the admin panel.
Caveat Review a-blog cms release notes for your version branch before upgrading, as minor version upgrades may include feature changes or configuration adjustments.

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
  • Testing3.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,390
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,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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