CVE-2024-46085
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedFrogCMS V0.9.5 was discovered to contain a Cross-Site Request Forgery (CSRF) vulnerability via /admin/?/plugin/file_manager/rename
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceFrogCMS v0.9.5 contains a CSRF vulnerability in the file_manager plugin's rename function at /admin/?/plugin/file_manager/rename. The endpoint lacks anti-CSRF token protection, allowing authenticated administrators to be tricked into renaming files via malicious crafted requests from other sites.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 0.9.5CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Confirm FrogCMS version 0.9.5 is installedCheck the version file or dashboard footer for the FrogCMS version number. Common locations include a VERSION file in the root directory or displayed in the admin panel footer.Affected if The installed version is exactly 0.9.5
-
Verify file_manager plugin is enabledNavigate to the admin panel Plugins section or check the plugins configuration file to confirm the file_manager plugin is active.Affected if The file_manager plugin is installed and enabled in FrogCMS 0.9.5
-
Inspect rename form for anti-CSRF tokenAccess the rename functionality at /admin/?/plugin/file_manager/rename in a browser, view the page source, and search for a CSRF token input field (commonly named token, csrf_token, or similar) or any hidden form field used for CSRF protection.Affected if The rename form does NOT contain any anti-CSRF token field (the absence of a token field indicates vulnerability)
-
Check server-side token validation in rename handlerExamine the server-side code for the file_manager rename action (typically in the plugin PHP files) to verify if the rename request validates a CSRF token before processing the rename operation.Affected if The rename handler does NOT validate an anti-CSRF token server-side
A user is affected if running FrogCMS 0.9.5 with the file_manager plugin enabled and the rename form lacks anti-CSRF token protection.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataImplement synchronizer token pattern (anti-CSRF tokens) for all state-changing operations in the file_manager plugin, validate tokens server-side, and consider SameSite cookie attributes to mitigate CSRF attacks.
- Consultation3.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-46085 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-46085 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data