Remove Slug From Custom Post TypeWordPress extension · Joakimling
CVE-2023-44238
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 Joakim Ling Remove slug from custom post type plugin <= 1.0.3 versions.
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 confidenceCross-Site Request Forgery (CSRF) vulnerability in the 'Remove slug from custom post type' WordPress plugin versions 1.0.3 and below. Attackers can craft malicious links that, when clicked by an authenticated administrator, can trigger unintended state-changing actions on the plugin (such as modifying custom post type slug settings) without the user's consent.
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
Remove Slug From Custom Post TypeWordPress extension
<= 1.0.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.
-
Verify plugin installationCheck if the 'Joakimling Remove Slug From Custom Post Type' plugin is present in your WordPress installation. Navigate to Plugins > Installed Plugins in the WordPress admin dashboard and look for this specific plugin name.Affected if The plugin is listed in the installed plugins page
-
Check installed versionIn the WordPress admin, go to Plugins > Installed Plugins and find the 'Joakimling Remove Slug From Custom Post Type' plugin. Note the version number displayed under the plugin name.Affected if The version listed is 1.0.3 or lower
-
Confirm admin authentication requirementUnderstand that this is a CSRF vulnerability that requires an authenticated administrator to click a malicious link. The attack only affects users who are logged in as administrators with permissions to modify the plugin settings.Affected if An administrator session is active and the plugin is installed at a vulnerable version
-
Inspect plugin for nonce implementation (optional deeper check)If you have file access, examine the plugin PHP files (typically in wp-content/plugins/remove-slug-from-custom-post-type/) and search for nonce verification functions like wp_verify_nonce, check_admin_referer, or nonces in form hidden fields.Affected if No nonce verification is found in files that handle settings modifications or state-changing actions
You are affected if the 'Joakimling Remove Slug From Custom Post Type' plugin is installed at version 1.0.3 or below and an authenticated administrator can be tricked into clicking a malicious link.
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 dataAdd anti-CSRF tokens (nonces) to all form submissions and AJAX actions in the plugin that modify settings or perform state changes. Validate the HTTP Referer header and implement SameSite cookie attributes. Alternatively, update to a patched version if released by the vendor.
Fix this in Remove Slug From Custom Post Type
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing2.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 $2,848.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-44238 — 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-2023-44238 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