dbcve.org
Advanced Custom FieldsApplication · Tassos

CVE-2026-48906

HIGH · 8.1 CVSS v3.1 Published 2026-05-27
Fix available
A fix is available. Upgrade to after 7.1.1 or later.
See remediation →
87/100
Remediation priority · High
Remotely reachable Zero-click

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
The vulnerability in the Tassos Framework Plugin allows users to delete arbitrary files on the affected sites.

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 · moderate confidence

The Tassos Framework Plugin contains an Insecure Direct Object Reference (IDOR) vulnerability allowing authenticated users to delete arbitrary files on affected sites. This arbitrary file deletion vulnerability has a CVSS score of 8.1, indicating high severity due to the potential for complete site compromise through systematic file removal.

MitigationImmediately update the Tassos Framework Plugin to the latest patched version when available. Review user role permissions and restrict file deletion capabilities to only trusted administrators until the patch is applied.

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
Advanced Custom FieldsApplication
Affected:>= 1.0.0, <= 2.8.12>= 3.0.0, <= 3.1.3
Convert FormsApplication
Affected:>= 1.0.0, <= 4.4.12>= 5.0.0, <= 5.1.5
EngageboxApplication
Affected:>= 1.0.0, <= 6.3.11>= 7.0.0, <= 7.1.1
Google Structured DataApplication
Affected:>= 1.0.0, <= 5.6.11>= 6.0.0, <= 6.1.9
Mailchimp Auto SubscribeApplication
Affected:>= 1.0.0, <= 5.0.5>= 5.1.0, <= 5.2.0
Smile PackApplication
Affected:>= 1.0.0, <= 1.2.6>= 2.0.0, <= 2.1.0
Tassos Code SnippetsApplication
Affected:= 1.0.0
Tassos FrameworkApplication
Affected:>= 1.0.0, <= 6.0.1

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
High

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

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

  1. Identify installed Tassos plugins
    Check the wp-content/plugins/ directory for folders starting with 'tassos', 'convert-forms', 'engagebox', 'google-structured-data', 'mailchimp-auto-subscribe', 'smile-pack', or 'tassos-framework'. Also check the plugins list in the WordPress admin under Plugins > Installed Plugins.
    Affected if Any of the eight affected Tassos plugins (Advanced Custom Fields, Convert Forms, Engagebox, Google Structured Data, Mailchimp Auto Subscribe, Smile Pack, Tassos Code Snippets, or Tassos Framework) are installed.
  2. Locate plugin version information
    Open the main plugin PHP file (usually named the same as the plugin folder with a .php extension) and look for a version comment or the 'Version' header in the plugin file header comments.
    Affected if Unable to locate version information in the plugin files.
  3. Compare installed version against affected ranges
    Compare the installed version number to these affected ranges: Tassos Framework <= 6.0.1; Advanced Custom Fields <= 2.8.12 or 3.0.0-3.1.3; Convert Forms <= 4.4.12 or 5.0.0-5.1.5; Engagebox <= 6.3.11 or 7.0.0-7.1.1; Google Structured Data <= 5.6.11 or 6.0.0-6.1.9; Mailchimp Auto Subscribe <= 5.0.5 or 5.1.0-5.2.0; Smile Pack <= 1.2.6 or 2.0.0-2.1.0; Tassos Code Snippets = 1.0.0
    Affected if The installed version falls within any of the listed affected version ranges.
  4. Check for file deletion functionality exposure
    Review the plugin code for any AJAX actions or endpoints that handle file deletion operations, typically involving functions like wp_delete_file, unlink, or delete_file. Look for parameters that accept file paths without proper authorization checks.
    Affected if The plugin exposes file deletion functionality accessible to authenticated users without proper access controls.

A user is affected if any of the eight Tassos plugins is installed with a version number matching the affected ranges, as the IDOR vulnerability allows authenticated users to delete arbitrary files.

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 7.1.1
Interim mitigation

Immediately update the Tassos Framework Plugin to the latest patched version when available. Review user role permissions and restrict file deletion capabilities to only trusted administrators until the patch is applied.

Recommended fix Moderate confidence

Upgrade to the latest version of the affected Tassos Framework-based plugin available from tassos.gr (version higher than 6.0.1 for Tassos Framework)

  1. 1. Identify the specific Tassos Framework-based plugin affected in your installation (Advanced Custom Fields, Convert Forms, Engagebox, Google Structured Data, Mailchimp Auto Subscribe, Smile Pack, Tassos Code Snippets, or Tassos Framework itself)
  2. 2. Check the currently installed version of the affected plugin in your WordPress or Joomla admin panel
  3. 3. Visit the official vendor source at tassos.gr to obtain the latest version of the affected plugin
  4. 4. Update the plugin to the latest version available from the vendor which contains the security fix
  5. 5. Verify the update was successful by confirming the new version number in the admin panel
  6. 6. Test that the plugin functionality remains intact after the update
Caveat Review plugin changelog for any breaking changes between your current version and the new version

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

Fix this in Advanced Custom Fields Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get the upgrade done

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-48906 — 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-2026-48906 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