Add Shortcodes Actions And FiltersWordPress extension · Add Shortcodes Actions And Filters Project
CVE-2023-44475
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 Michael Simpson Add Shortcodes Actions And Filters plugin <= 2.0.9 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 WordPress plugin 'Add Shortcodes Actions And Filters' versions 2.0.9 and below allows attackers to potentially trick authenticated administrators into performing unintended actions by leveraging the lack of proper nonce validation on plugin functions.
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
Add Shortcodes Actions And FiltersWordPress extension
<= 2.0.9CVSS 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 is installedCheck your WordPress installation under wp-content/plugins/ for a folder named 'add-shortcodes-actions-and-filters' or 'ashaf', or view the installed plugins list in the WordPress admin dashboard under Plugins > Installed PluginsAffected if The plugin folder exists in the plugins directory or appears in the WordPress admin plugin list
-
Confirm plugin versionIn WordPress admin, go to Plugins > Installed Plugins and look for 'Add Shortcodes Actions And Filters' to view the version number displayed below the plugin name, or open the main plugin file (usually add-shortcodes-actions-and-filters.php) and check the 'Version' header in the plugin comment blockAffected if The displayed version number is 2.0.9 or lower
-
Check if plugin is activeIn WordPress admin under Plugins > Installed Plugins, verify whether 'Add Shortcodes Actions And Filters' shows as 'Active' under the plugin statusAffected if The plugin shows as Active and the version is 2.0.9 or below
Your environment is affected if the Add Shortcodes Actions And Filters plugin is active and the installed version is 2.0.9 or lower, since these versions lack proper nonce validation on plugin functions enabling CSRF attacks.
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.
dbcve · scopedUpdate the plugin to version 2.0.10 or later which contains the fix; alternatively, disable the plugin until an update is available.
2.1.0 or latest available version
- 1. Log in to the WordPress admin dashboard
- 2. Navigate to Plugins > Installed Plugins
- 3. Locate 'Add Shortcodes Actions And Filters' in the plugin list
- 4. If an update is available, click 'Update Now' to install the latest version
- 5. Verify the update was successful by checking the plugin version after updating
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Add Shortcodes Actions And Filters
Scoped from the published advisory
- 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-2023-44475 — 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-44475 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