cve.bz

CVE-2026-110025 slackero phpwcms: Improper Access Control

6.9 mediumEPSS 0.4%

Medium (6.9) in slackero phpwcms. EPSS 0.4% estimated probability of exploitation activity in the next 30 days.

On this page
A flaw has been found in slackero phpwcms up to 1.9.49/1.12.3. This issue affects some unknown processing of the file include/inc_front/content/cnt23.article.inc.php of the component Extension Check. This manipulation of the argument POST_name causes unrestricted upload. The attack can be initiated remotely. Upgrading to version 1.9.50 and 1.12.4 is capable of addressing this issue. Patch name: 118c978430f5a9668b30535f6e592c7ae8df711f/f4c136b467565b2d16ebe2b8276b9a03547a9a69/8571cb47df8d66804d1eb88ae3d1ab4fb513e1e7. Upgrading the affected component is recommended.

Severity

CVSS 4.0

6.9 medium
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N

CVSS 3.1

7.3 high
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L
EPSS
0.4% (unchanged from 0.4% a week ago; 0.4% 30 days ago) estimated probability of exploitation activity in the next 30 days; 32nd percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: PoC · Automatable: yes · Technical impact: partial, assessed 2026-10-15. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWEs
CWE-284 Improper Access Control
CWE-434 Unrestricted Upload of File with Dangerous Type
OWASP Top 10
A01:2025 Broken Access Control, A06:2025 Insecure Design
Published
Modified
NVD analysis
Deferred: the NVD does not plan to analyze it
Record from
the NVD, synced

Ask an AI about this CVE

Show the promptExplain CVE-2026-110025 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-110025?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-110025?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-110025 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
slackero phpwcms1.9.0
slackero phpwcms1.9.1
slackero phpwcms1.9.2
slackero phpwcms1.9.3
slackero phpwcms1.9.4
slackero phpwcms1.9.5
slackero phpwcms1.9.6
slackero phpwcms1.9.7
slackero phpwcms1.9.8
slackero phpwcms1.9.9
slackero phpwcms1.9.10
slackero phpwcms1.9.11
slackero phpwcms1.9.12
slackero phpwcms1.9.13
slackero phpwcms1.9.14
slackero phpwcms1.9.15
slackero phpwcms1.9.16
slackero phpwcms1.9.17
slackero phpwcms1.9.18
slackero phpwcms1.9.19
slackero phpwcms1.9.20
slackero phpwcms1.9.21
slackero phpwcms1.9.22
slackero phpwcms1.9.23
slackero phpwcms1.9.24
slackero phpwcms1.9.25
slackero phpwcms1.9.26
slackero phpwcms1.9.27
slackero phpwcms1.9.28
slackero phpwcms1.9.29
slackero phpwcms1.9.30
slackero phpwcms1.9.31
slackero phpwcms1.9.32
slackero phpwcms1.9.33
slackero phpwcms1.9.34
slackero phpwcms1.9.35
slackero phpwcms1.9.36
slackero phpwcms1.9.37
slackero phpwcms1.9.38
slackero phpwcms1.9.39
slackero phpwcms1.9.40
slackero phpwcms1.9.41
slackero phpwcms1.9.42
slackero phpwcms1.9.43
slackero phpwcms1.9.44
slackero phpwcms1.9.45
slackero phpwcms1.9.46
slackero phpwcms1.9.47
slackero phpwcms1.9.48
slackero phpwcms1.9.49
slackero phpwcms1.12.0
slackero phpwcms1.12.1
slackero phpwcms1.12.2
slackero phpwcms1.12.3

GitHub PoC

Repositories on GitHub named after this CVE or listed for it by the PoC-in-GitHub index. For those marked Harbor Check: matches CVE, Flawharbor read the code and found it implements this CVE's exploitation technique: read, not run, and its dependencies only checked for warning signs, so a pointer and no guarantee. The rest are unverified: some hold a working proof of concept, some nothing useful, and some malware made to look like one. Read the code before you run any of it. How Harbor Check reads them, and what it found.

  • capivara-research/CVE-2026-110025 Harbor Check: matches CVE 0 stars, Shell, created
    CVE-2026-110025: bilingual analysis and safe local PoC for phpwcms unrestricted upload to RCE

Attack patterns (CAPEC)

  • CAPEC-1 Accessing Functionality Not Properly Constrained by ACLs Likelihood: High · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits. More on the page of CWE-284 (17).

References

Check your stackJSON