playSMS before 1.4.5 allows Arbitrary Code Execution by entering PHP code at the #tabs-information-page of core_main_config, and then execu…

published 2021-09-10 5y ago modified 2026-06-17 4mo ago also EUVD-2021-27550

cvss: 9.8; version 3.1, NVD
cisa kev: Not listed; not in CISA's catalog
epss: 4.7%; EPSS 4.7% chance of exploitation in 30 days, percentile 91%
public exploits: 0; none known

playSMS before 1.4.5 allows Arbitrary Code Execution by entering PHP code at the #tabs-information-page of core_main_config, and then executing that code via the index.php?app=main&inc=core_welcome URI.

Patch / fix

fixed in 1

playsms playsms 1.4.5

Is CVE-2021-40373 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Exploit prediction

4.74% chance of exploitation in the next 30 days, higher than 91% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

github.com https://github.com/maikroservice/CVE-2021-40373 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by	version	score	vector
NVD	3.1	9.8	CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
NVD	2.0	7.5	AV:N/AC:L/Au:N/C:P/I:P/A:P

Classification

Weakness

CWE-94 Improper Control of Generation of Code

References

github.com /maikroservice/CVE-2021-40373
exploit, third-party-advisory
playsms.org /2021/09/04/playsms-1-4-5-released/
release-notes, vendor-advisory

Sources

CVE List CVE-2021-40373
NVD CVE-2021-40373

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.