dbcve.org
HermitWordPress extension · Hermit Project

CVE-2022-29412

MEDIUM · 5.4 CVSS v3.1 Published 2022-04-28
Fix available
A fix is available. Upgrade to after 3.1.6 or later.
See remediation →
61/100
Remediation priority · Elevated
Remotely reachable No privileges

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 · unedited
Multiple Cross-Site Request Forgery (CSRF) vulnerabilities in Hermit 音乐播放器 plugin <= 3.1.6 on WordPress allow attackers to delete cache, delete a source, create source.

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 confidence

Multiple Cross-Site Request Forgery (CSRF) vulnerabilities in the Hermit 音乐播放器 WordPress plugin versions 3.1.6 and below allow authenticated attackers to delete cache, delete audio sources, and create new sources by tricking authenticated users into submitting malicious requests.

MitigationImplement anti-CSRF nonce validation on all state-changing operations (cache deletion, source deletion, source creation) and update to the latest patched version of the plugin.

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
HermitWordPress extension
Affected:<= 3.1.6

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
Unchanged
Confidentiality
None
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Check if Hermit plugin is installed
    Navigate to WordPress Admin > Plugins > Installed Plugins and look for 'Hermit' or 'Hermit 音乐播放器' in the list. Alternatively, check the /wp-content/plugins/ directory for a hermit folder.
    Affected if The Hermit plugin is found in the WordPress installation
  2. Identify the installed Hermit plugin version
    In WordPress Admin > Plugins, find the Hermit plugin entry and read the version number displayed below the plugin name. If using FTP/shell, check the main plugin file (usually hermit.php) for the 'Version' header in the plugin comment block.
    Affected if The version number is 3.1.6 or lower
  3. Verify the plugin is active
    In WordPress Admin > Plugins > Installed Plugins, confirm the Hermit plugin shows as 'Active' under the plugin status column.
    Affected if The plugin is currently active and the version is 3.1.6 or lower
  4. Confirm the WordPress user roles present
    In WordPress Admin > Users, review which user accounts exist. CSRF attacks require a logged-in authenticated user to trigger the malicious request.
    Affected if Any user with contributor-level or higher access exists on the site and the Hermit plugin version is 3.1.6 or lower
  5. Review Hermit plugin source files for nonce validation
    If you have file access, examine the PHP files handling cache deletion and audio source management (typically in the plugin's admin or core files). Search for the presence of 'wp_verify_nonce' or 'check_admin_referer' function calls on state-changing operations.
    Affected if State-changing actions (cache deletion, source creation/deletion) lack nonce validation code and the plugin version is 3.1.6 or lower

You are affected if the Hermit WordPress plugin version 3.1.6 or lower is installed and active on your WordPress site, with authenticated users present.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Upgrade available Upgrade to a release after 3.1.6
Interim mitigation

Implement anti-CSRF nonce validation on all state-changing operations (cache deletion, source deletion, source creation) and update to the latest patched version of the plugin.

Recommended fix Moderate confidence

Upgrade to the latest available version of Hermit (音乐播放器) plugin (currently available on wordpress.org)

  1. 1. Log in to your WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate the Hermit (音乐播放器) plugin
  4. 4. If an update is available, click 'Update Now' to install the latest version
  5. 5. After updating, verify the plugin is running on a version higher than 3.1.6
  6. 6. Test that plugin functionality remains intact after the update
  7. 7. Consider implementing anti-CSRF tokens (nonces) in custom code if using the plugin's AJAX endpoints

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Hermit Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA3.0 h
16.0 hours of engineering $2,820
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,512.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-29412 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-29412 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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