CVE-2024-40522: There is a remote code execution vulnerability in SeaCMS 12.9.
Noroxi assessment
Priority: Monitor (action score 35/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 1.1% (FIRST EPSS); higher than 67.2% of all records.
- Anyone who can reach it over the internet can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- According to the record, no fixed version is available yet.
Low priority for now. Update when a fix is released; follow the vendor's advisory.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
There is a remote code execution vulnerability in SeaCMS 12.9. The vulnerability is caused by phomebak.php writing some variable names passed in without filtering them before writing them into the php file. An authenticated attacker can exploit this vulnerability to execute arbitrary commands and obtain system permissions.
- Published
- Jul 12, 2024
- Updated
- Jun 17, 2026
- EPSS
- 1.1% · 67th percentile
- CWE
- CWE-94
Report tools
Action score
35
Monitor
Low priority for now.
- CVSS
- 35 / 40 · 8.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 1.1%
CISA SSVC decision
- Exploitation
- proof of concept
- Automatable
- no
- Technical impact
- total
Vulnrichment: CISA's decision-tree inputs.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- No fixed version yet
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| seacms | seacms | cpe:2.3:a:seacms:seacms |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- seacms seacms12.9
Same product
seacms: all recordsOther highest-scoring records for the same primary product.
- CVE-2022-27336Seacms v11.6 was discovered to contain a remote code execution (RCE) vulnerability via the component /admin/weixin.php.45Plan
- CVE-2024-29275SQL injection vulnerability in SeaCMS version 12.9, allows remote unauthenticated attackers to execute arbitrary code and obtain sensitive i40Plan
- CVE-2022-23878seacms V11.5 is affected by an arbitrary code execution vulnerability in admin_config.php.40Plan
Published before and after this one in the same product
- ← EarlierCVE-2024-40520Jul 12, 2024 · SeaCMS 12.9 has a remote code execution vulnerability.35Monitor
- ← EarlierCVE-2024-40521Jul 12, 2024 · SeaCMS 12.9 has a remote code execution vulnerability.35Monitor
- Later →CVE-2024-39036Jul 16, 2024 · SeaCMS v12.9 is vulnerable to Arbitrary File Read via admin_safe.php.26Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
No fix version is recorded for this entry. Check the references for vendor advisories.
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
- CVE-2024-4664070 days apartSeaCMS 13.2 has a remote code execution vulnerability located in the file sql.class.chp.39Monitor
- CVE-2023-46010261 days apartAn issue in SeaCMS v.12.9 allows an attacker to execute arbitrary commands via the admin_safe.php component.39Monitor
- CVE-2023-43222289 days apartSeaCMS v12.8 has an arbitrary code writing vulnerability in the /jxz7g2/admin_ping.php file.39Monitor
- CVE-2025-44071297 days apartSeaCMS v13.3 was discovered to contain a remote code execution (RCE) vulnerability via the component phomebak.php.39Monitor
- CVE-2024-405210 days apartSeaCMS 12.9 has a remote code execution vulnerability.35Monitor
- CVE-2024-4259941 days apartSeaCMS 13.0 has a remote code execution vulnerability.35Monitor
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-94 · Improper Control of Generation of Code ('Code Injection')CVSS vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
Change log
No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.