CVE Intelligence
Skip to main content
MEDIUM

CVE-2024-31396

CVE-2024-31396 Vulnerability Analysis & Exploit Intelligence

Code injection vulnerability exists in a-blog cms Ver.3.1.x series versions prior to Ver.3.1.12 and Ver.3.0.x series versions prior to Ver.3.0.32. If this vulnerability is exploited, a user with an administrator or higher privilege who can log in to the product may execute an arbitrary command on the server.

Published Updated Sources: cvelistV5, jpcert

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the scoring sources call it.

Exploitation

Unreported

no source claims exploitation

EPSS

0%

chance of exploitation in 30 days

Affects

appleple

3 products listed

CVSS base

6.6

MEDIUM

CISA SSVC assessment

Three decision points CISA publishes for the CVEs it assesses · SSVC 2.0.3. A stakeholder decision, not a severity score.

CISA

Exploitation

None

none · proof-of-concept · active

Automatable

No

can an attacker script all four kill-chain steps

Technical impact

Total

partial · total control of the vulnerable component

Affected scope

The catalog records vendors and products as separate lists, not pairs, so which product belongs to which vendor is not something this page can say.

Vendors (1)

appleple

Products (3)

a blog cms ver 3 1 x seriesa blog cms ver 3 0 x seriesa blog cms

Every base score collected

Sources score independently and disagree; each row says who scored it and under which version.

ScoreVersionSeverityExpl.ImpactSource
6.6CVSS 3.1MEDIUM——cvelistV5

Weakness & attack patterns

  • CWE-94

Attack patterns reported against this CVE. The ATT&CK techniques below are inferred from its weakness class.

  • T1027.006Obfuscated Files or Information: HTML Smuggling
  • T1027.009Obfuscated Files or Information: Embedded Payloads
  • T1564.009Hide Artifacts: Resource Forking

References

2 on the record

Elsewhere on this site

  • applepleevery CVE for this vendor
  • CWE-94other pages naming this weakness

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

  • No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
  • No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
  • No exploit packet captures, log samples, or incident case IDs supplied.