GHSA-2hpc-mf4q-j885: Silverstripe CSRF vulnerability in GridFieldAddExistingAutocompleter
Noroxi assessment
Priority: Monitor (action score 17/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Anyone who can reach it over the internet can trigger it. No account or password is required. A user must open a link or visit a page. No special conditions are required; it is repeatable.
- Fixed version: silverstripe/framework (Packagist) 3.2.2, 3.3.0, 3.1.17.
Low priority for now. Upgrade to silverstripe/framework (Packagist) 3.2.2, 3.3.0, 3.1.17 or later.
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: OSV
GridField does not have sufficient CSRF protection, meaning that in some cases users with CMS access can be tricked into posting unspecified data into the CMS from external websites. Amongst other default CMS interfaces, GridField is used for management of groups, users and permissions in the CMS. The resolution for this issue is to ensure that all gridFieldAlterAction submissions are checked for the SecurityID token during submission.
- Published
- May 23, 2024
- Updated
- Nov 28, 2024
- EPSS
- —
- CWE
- CWE-352
Report tools
Action score
17
Low priority for now.
- CVSS
- 17 / 40 · 4.3 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · —
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi 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 |
|---|---|---|
| Packagist | silverstripe/framework | pkg:composer/silverstripe/framework |
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Packagist | silverstripe/framework | from 3.2.0 · before 3.2.2 | 3.2.2 |
| Packagist | silverstripe/framework | from 3.3.0-beta1 · before 3.3.0 | 3.3.0 |
| Packagist | silverstripe/framework | before 3.1.17 | 3.1.17 |
Same product
Packagist: all recordsOther highest-scoring records for the same primary product.
- GHSA-8v6m-7f5v-hhx6Silverstripe Brute force bypass on default admin36Monitor
- GHSA-265q-222x-52m6silverstripe/framework has potential SQL Injection vulnerability in PostgreSQL database connector35Monitor
- GHSA-vcg6-8fxc-x5cqsilverstripe/framework allows upload of dangerous file types35Monitor
Published before and after this one in the same product
- ← EarlierGHSA-qp29-wcc2-vmpcMay 23, 2024 · Silverstripe HtmlEditor embed url sanitisation17Monitor
- ← EarlierGHSA-x5w2-wcr8-9q45May 23, 2024 · Silverstripe Missing security check on dev/build/defaults26Monitor
- Later →GHSA-87pf-7x99-5xc4May 23, 2024 · Silverstripe Hostname, IP and Protocol Spoofing through HTTP Headers26Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Packagist:silverstripe/framework | 3.1.17 | Package registry (OSV) |
| Packagist:silverstripe/framework | 3.2.2 | Package registry (OSV) |
| Packagist:silverstripe/framework | 3.3.0 | Package registry (OSV) |
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.
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
- GHSA-vj2j-6g3w-46620 days apartSilverstripe Missing CSRF protection in login form21Monitor
Not on record for this CVE: EPSS history · researcher credit · public bounty program.
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- A user must open a link or visit a page.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- low · data or configuration can be modified
- Availability
- none
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- Low
- Availability impact
- None
Weakness class (CWE)
CWE-352 · Cross-Site Request Forgery (CSRF)CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N
osv
Root cause
State-changing requests rely on the session cookie the browser sends automatically; nothing verifies that the request came from the user’s own page.
The bug in code
The whole CWE-352 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
app.use(session({ cookie: { httpOnly: true } }));
app.post("/account/address", updateAddress);Fixed
app.use(session({ cookie: { httpOnly: true, sameSite: "lax" } }));
app.post("/account/address", csrfProtection, updateAddress);Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (5 more)Show less
- github.com/silverstripe/silverstripe-framework/commit/56e92f5a32e45849cc9361c8603c31d7010c9d36
- github.com/silverstripe/silverstripe-framework/commit/e2c77c5a8f13e901c51a3684210811559b592f0c
- github.com/FriendsOfPHP/security-advisories/blob/master/silverstripe/framework/SS-2016-002-1.yaml
- github.com/silverstripe/silverstripe-framework
- www.silverstripe.org/download/security-releases/ss-2016-002
Vendor advisories and official records. Exploit/PoC links are deliberately left out.