HermitWordPress extension · Hermit Project
CVE-2022-29411
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 · uneditedSQL Injection (SQLi) vulnerability in Mufeng's Hermit 音乐播放器 plugin <= 3.1.6 on WordPress allows attackers to execute SQLi attack via (&id).
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 confidenceCritical SQL injection vulnerability in the Mufeng Hermit WordPress music player plugin allows remote attackers to inject arbitrary SQL commands via the &id parameter. This pre-authentication flaw in versions <=3.1.6 can lead to complete database compromise including extraction of sensitive data, user credentials, and potential escalation to remote code execution.
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
<= 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
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/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 Hermit plugin is installedCheck your WordPress plugins directory for the hermit folder, or query the WordPress database: SELECT * FROM wp_options WHERE option_name = 'active_plugins';Affected if The hermit plugin appears in the active plugins list or plugin directory.
-
Identify installed Hermit versionCheck the hermit.php file header for the Version comment, or query: SELECT option_value FROM wp_options WHERE option_name = 'hermit_version';Affected if The installed version is 3.1.6 or lower.
-
Verify plugin is activeCheck WordPress admin panel plugins list or query active_plugins option as above.Affected if Hermit plugin shows as active.
-
Identify exposed endpointThe vulnerable URL pattern is any request to the plugin's ajax handler with an &id parameter, typically: /wp-admin/admin-ajax.php?action=hermit_load&playlist_id=1&id=[injection]Affected if The plugin handles requests with the &id parameter without authentication.
-
Review access logs for exploitation attemptsSearch web server access logs (Apache/nginx) for patterns like 'admin-ajax.php?action=hermit_load' combined with SQL injection payloads (UNION, SELECT, SLEEP, etc.) in the id parameter.Affected if Suspicious SQL injection patterns appear in logs targeting the hermit endpoint.
You are affected if Hermit plugin version 3.1.6 or lower is installed and active, exposing the &id parameter to unauthenticated requests.
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 dataImmediately update Hermit plugin to version >3.1.6 or remove the plugin if not needed; audit logs for signs of exploitation and consider database user password rotation given critical severity.
Fix this in Hermit
Scoped from the published advisory
- Consultation2.0 h
- Implementation1.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 $1,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-29411 — 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-29411 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