CVE-2025-31103

Untrusted data deserialization vulnerability exists in a-blog cms. Processing a specially crafted request may store arbitrary files on the server where the product is running. This can be leveraged to execute an arbitrary script on the server.

Published: 2025-03-31 Last update: 2025-05-13 Assigner: [email protected] Source: [email protected]
NVD Status：Analyzed，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2025-31103 is rated Moderate Risk (55.4/100): CVSS High severity, with medium exploitation likelihood (EPSS 0.71%). Review affected assets and schedule remediation.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2025-31103

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-05-11 0.58% 0.71% +0.13%
2 2026-05-06 0.43% 0.58% +0.15%
3 2026-01-25 — 0.43% —

Full EPSS history (8 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2025-31103

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
7.5 3.1 HIGH
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:N)
Doesn’t really leak secrets in a meaningful way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:N)
Service keeps running; no real outage angle.
 3.9 3.6 [email protected]
7.5 3.0 HIGH
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:N)
Doesn’t really leak secrets in a meaningful way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:N)
Service keeps running; no real outage angle.
 3.9 3.6 [email protected]

Weakness enumeration for CVE-2025-31103

Affected software / configurations for CVE-2025-31103

Vendor Product Version Raw CPE
appleple a-blog_cms <= 2.8.80 cpe:2.3:a:appleple:a-blog_cms:*:*:*:*:*:*:*:*
appleple a-blog_cms >= 2.9.0, <= 2.9.46 cpe:2.3:a:appleple:a-blog_cms:*:*:*:*:*:*:*:*
appleple a-blog_cms >= 2.10.0, < 2.10.58 cpe:2.3:a:appleple:a-blog_cms:*:*:*:*:*:*:*:*
appleple a-blog_cms >= 2.11.0, < 2.11.70 cpe:2.3:a:appleple:a-blog_cms:*:*:*:*:*:*:*:*
appleple a-blog_cms >= 3.0.0, < 3.0.41 cpe:2.3:a:appleple:a-blog_cms:*:*:*:*:*:*:*:*
appleple a-blog_cms >= 3.1.0, < 3.1.37 cpe:2.3:a:appleple:a-blog_cms:*:*:*:*:*:*:*:*

References for CVE-2025-31103

cvelogic Threat Intelligence