CVE-2022-29413
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) leading to Stored Cross-Site Scripting (XSS) in Mufeng's Hermit 音乐播放器 plugin <= 3.1.6 on WordPress via &title parameter.
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 confidenceThe Hermit 音乐播放器 WordPress plugin versions 3.1.6 and below is vulnerable to Cross-Site Request Forgery (CSRF) that enables Stored Cross-Site Scripting (XSS). Attackers can trick authenticated administrators into clicking malicious links, causing the browser to send crafted requests that inject malicious JavaScript via the &title parameter, which is then stored and executed when other users view the affected content.
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<= 3.1.6CVSS 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
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
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 Hermit plugin installationLog into WordPress admin dashboard and navigate to Plugins > Installed Plugins. Look for 'Hermit 音乐播放器' or 'Hermit' in the plugin list.Affected if The plugin is not installed or is not present in the WordPress installation.
-
Identify installed Hermit versionIn the WordPress admin, find the Hermit plugin entry in the Plugins list. The version number is displayed below the plugin name. Alternatively, inspect the file /wp-content/plugins/hermit/class.php or the main plugin header file and locate the 'Version:' comment.Affected if The installed version is 3.1.6 or lower.
-
Check if playlist or playlist item creation is accessibleNavigate to the Hermit plugin settings or playlist management section in WordPress admin. Look for options to create or edit playlists where the title parameter would be used.Affected if The plugin allows creating or editing playlists/playlist items where a title field is present.
-
Inspect title parameter handling for lack of sanitizationIf you have code access, examine the PHP file that handles playlist title input (typically in the plugin admin panel or shortcode handler). Look for functions like sanitize_text_field, esc_html, or wp_kses applied to the title parameter.Affected if The code does not sanitize or escape the title parameter before storage or output, or no anti-CSRF nonce verification is present in the form handling.
You are affected if the Hermit plugin is installed with version 3.1.6 or lower and playlist title editing functionality is accessible without proper CSRF protection and input sanitization.
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 dataUpdate the Hermit 音乐播放器 plugin to the latest patched version. Additionally, implement anti-CSRF tokens (nonces) for state-changing operations and ensure all user-supplied input, especially the title parameter, is properly sanitized and escaped before storage and output.
- Consultation2.0 h
- Implementation3.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,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-29413 — 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-2022-29413 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