Frontpage ManagerWordPress extension · Elisebosse
CVE-2024-22285
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 · uneditedCross-Site Request Forgery (CSRF) vulnerability in Elise Bosse Frontpage Manager.This issue affects Frontpage Manager: from n/a through 1.3.
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 · moderate confidenceCross-Site Request Forgery (CSRF) vulnerability in Elise Bosse Frontpage Manager allows attackers to trick authenticated users into performing unintended administrative actions on the plugin, such as modifying frontpage configurations, through maliciously crafted requests.
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
Frontpage ManagerWordPress extension
<= 1.3CVSS 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 Elisebosse Frontpage Manager is installedLocate the plugin in the WordPress plugin directory or check the plugin files for 'elisebosse-frontpage-manager' or similar namingAffected if Plugin is present and active in the CMS
-
Identify installed plugin versionCheck the plugin header in its main PHP file or the WordPress plugin admin page for the version numberAffected if Version is 1.3 or lower
-
Verify authenticated admin access existsConfirm that administrative user accounts exist and can access the WordPress admin dashboard where the plugin operatesAffected if Admin users can log in and access the plugin settings
-
Inspect plugin forms for CSRF protectionExamine the plugin admin pages containing forms (such as frontpage configuration settings) and look for a CSRF token field (often named '_wpnonce', 'nonce', 'csrftoken', or similar) in each formAffected if Forms that modify plugin settings lack CSRF token fields
-
Inspect AJAX endpoints for CSRF protectionUse browser developer tools or HTTP intercepting proxy to examine AJAX requests made by the plugin. Check if the requests include anti-CSRF token parametersAffected if AJAX requests that modify plugin state do not include CSRF token parameters
User is affected if Elisebosse Frontpage Manager version 1.3 or lower is installed, the plugin is active, and the plugin's forms or AJAX endpoints used for state-changing operations lack CSRF token validation.
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 anti-CSRF tokens (synchronizer token pattern) on all state-changing operations (forms and AJAX endpoints) in the Frontpage Manager plugin and validate these tokens on the server side before processing any modifications.
Fix this in Frontpage Manager
Scoped from the published advisory
- Consultation2.0 h
- Implementation6.0 h
- Testing3.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 $3,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-22285 — 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-22285 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