dbcve.org
A Blog CmsApplication · Appleple

CVE-2024-23180

HIGH · 8.8 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 →
94/100
Remediation priority · Urgent
Remotely reachable 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
Improper input validation 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 arbitrary code by uploading a specially crafted SVG file.

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 Improper input validation vulnerability in a-blog cms allows authenticated users to upload specially crafted SVG files that can contain embedded malicious scripts or exploit SVG parsing flaws, leading to arbitrary code execution on the server.

MitigationUpdate to the patched versions (3.1.7, 3.0.29, 2.11.58, 2.10.50 or later). Alternatively, disable or restrict SVG file uploads and sanitize existing SVG files.

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
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/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 a-blog cms installation
    Locate the a-blog cms installation directory and check for a version file or configuration that displays the installed version (commonly found in admin panel or version file in installation root)
    Affected if The installed version falls within any of these ranges: <= 2.9.0, >= 2.10.0 and < 2.10.50, >= 2.11.0 and < 2.11.58, >= 3.0.0 and < 3.0.29, or >= 3.1.0 and < 3.1.7
  2. Verify file upload capability is enabled
    Check the CMS configuration or admin settings to determine whether the file/media upload feature is available to authenticated users
    Affected if File upload functionality is enabled and accessible to authenticated users in the affected version ranges
  3. Confirm SVG file uploads are permitted
    Inspect the CMS upload settings or try to determine which file extensions are allowed for upload. Look for configuration that explicitly permits .svg files or check if there are no restrictions on image file type uploads
    Affected if SVG file extension is included in the allowed upload file types for authenticated users
  4. Review existing SVG uploads
    Search the media or upload directories for .svg files that may have been uploaded. Check file contents for embedded scripts or suspicious elements if accessible
    Affected if SVG files exist in the upload directories and the server is running an affected version

A user is affected if the installed a-blog cms version is within the vulnerable ranges AND authenticated users can upload SVG files to the server.

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

Update to the patched versions (3.1.7, 3.0.29, 2.11.58, 2.10.50 or later). Alternatively, disable or restrict SVG file uploads and sanitize existing SVG files.

Recommended fix High confidence

Upgrade to 3.1.7 (for 3.x series), 3.0.29 (for 3.0.x), 2.11.58 (for 2.11.x), or 2.10.50 (for 2.10.x) - choose the appropriate version based on your current major version branch

  1. 1. Identify the currently installed a-blog cms version by checking the admin panel or version file
  2. 2. Based on the current version, determine the appropriate upgrade path to a fixed release
  3. 3. Back up the entire a-blog cms installation including database and configuration files
  4. 4. Download the fixed version from the official a-blog cms website (developer.a-blogcms.jp)
  5. 5. Review upgrade documentation specific to your version path for any special migration steps
  6. 6. Install the new version following the standard upgrade procedure
  7. 7. Verify the installation by checking that file upload functionality works correctly with proper file type restrictions
  8. 8. Confirm the SVG upload vulnerability is resolved by testing with a crafted SVG file (should be rejected)
Caveat Review a-blog cms release notes for your version branch to check for any breaking changes or required migration steps between versions

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
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
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,272.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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