CVE-2024-54435
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 Thomas Hoefter Onlywire Multi Autosubmitter onlywire-multi-autosubmitter allows Stored XSS.This issue affects Onlywire Multi Autosubmitter: from n/a through <= 1.2.4.
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 the Onlywire Multi Autosubmitter WordPress plugin (versions <= 1.2.4) enables authenticated attackers to inject stored XSS payloads by tricking an administrator into submitting a crafted request. The lack of anti-CSRF tokens on state-changing forms allows attackers to perform actions on behalf of the victim, leading to persistent script injection.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS 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
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L
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.
-
Verify Onlywire Multi Autosubmitter plugin is installedCheck the WordPress plugins directory (wp-content/plugins/) for a folder containing 'onlywire' or check the Plugins page in WordPress admin for 'Onlywire Multi Autosubmitter'Affected if The plugin is present in the WordPress installation
-
Determine installed plugin versionOpen the main plugin PHP file (usually onlywire.php or similar in the plugin folder) and locate the Version header in the plugin comment block, or check the Plugins page in WordPress adminAffected if Version is 1.2.4 or lower
-
Inspect admin forms for anti-CSRF protectionNavigate to the plugin admin pages and view page source, or examine the plugin PHP files for state-changing forms (POST/GET requests that modify data) and check if they use wp_nonce_field, wp_nonce_url, or check_admin_referer functionsAffected if Forms handling submissions lack nonce verification code
-
Check input sanitization on stored dataReview plugin PHP code where user input is processed (typically in form handlers or admin menu callbacks) and verify if functions like sanitize_text_field, esc_html, or esc_attr are applied before storing or displaying dataAffected if User-supplied data is stored or output without proper sanitization functions
User is affected if the Onlywire Multi Autosubmitter plugin is installed at version 1.2.4 or lower and the plugin's state-changing forms lack anti-CSRF token verification.
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 (nonces) on all forms and state-changing operations, and apply proper output encoding/sanitization for all user-supplied data to prevent stored XSS.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-54435 — 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-54435 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