CVE-2025-51510 json
MoonShine SQL Injection Vulnerability
published last yr. modified last mo. also GHSA-9g9j-3w64-3cjh , EUVD-2025-25179
- cvss
- 4.9
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.5%
- EPSS 0.5% chance of exploitation in 30 days, percentile 45%
- public exploits
- 0
- none known
Summary
MoonShine was discovered to contain a SQL injection vulnerability under the Blog -> Categories page when using the moonshine-tree-resource (version < 2.0.2) component.
Patch / fix
- getmoonshine moonshine 2.0.2
Is CVE-2025-51510 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- Proof of concept is public
- Automatable
- no
- Technical impact
- partial
- Assessed
- last yr.
Exploit prediction
0.54% chance of exploitation in the next 30 days, higher than 45% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- github.com https://github.com/GiacoLenzo2109/MoonShine_Software_PoCs referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CISA ADP | 3.1 | 4.9 | CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N |
| CNA | 3.1 | 4.9 | CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N |
| GitHub | 3.1 | 4.9 | CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| packagist | moonshine/moonshine | <=3.12.5 |
no fix listed |
Classification
- Weakness
-
- CWE-89 Improper Neutralization of Special Elements used in an SQL Command
References
-
github.com
/GiacoLenzo2109/MoonShine_Software_PoCs
web, exploit, third-party-advisory
-
github.com
/moonshine-software/moonshine
package, product
-
github.com
/lee-to/moonshine-tree-resource
product
-
nvd.nist.gov
/vuln/detail/CVE-2025-51510
advisory
Sources
- CVE List CVE-2025-51510
- GitHub Advisory GHSA-9g9j-3w64-3cjh
- NVD CVE-2025-51510
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.