Ultimate Before After Image Slider \& GalleryWordPress extension · Themefic
CVE-2025-47549
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 · uneditedUnrestricted Upload of File with Dangerous Type vulnerability in Themefic BEAF beaf-before-and-after-gallery allows Upload a Web Shell to a Web Server.This issue affects BEAF: from n/a through <= 4.6.10.
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 confidenceThe Themefic BEAF beaf-before-and-after-gallery plugin lacks proper file type validation and access controls on its file upload functionality, allowing attackers to upload executable PHP files (web shells) directly to the web server. This unrestricted upload vulnerability enables remote code execution upon successful exploitation.
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
Ultimate Before After Image Slider \& GalleryWordPress extension
<= 4.6.10CVSS 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
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:H/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.
-
Verify BEAF plugin is installedCheck WordPress plugin directory for beaf-before-and-after-gallery folder, or look for 'Ultimate Before After Image Slider & Gallery' in wp-content/plugins/Affected if The BEAF plugin folder exists in the WordPress plugins directory
-
Identify installed BEAF versionRead the main plugin file (typically beaf-before-and-after-gallery/beaf.php) and locate the 'Version' header comment, or check in WordPress admin under Plugins > Installed PluginsAffected if Version is 4.6.10 or lower (any version <= 4.6.10 is affected)
-
Locate BEAF upload directoriesSearch wp-content/uploads/ for folders named 'beaf' or 'before-after', or inspect plugin code for upload path definitionsAffected if Upload directories exist and are writable by the web server
-
Check for suspicious PHP files in upload directoriesSearch wp-content/uploads/ and subdirectories for .php files, especially in beaf/before-after folders: find wp-content/uploads/ -name '*.php' -type fAffected if Any PHP files exist in upload directories (legitimate plugins should not place PHP there)
-
Verify PHP execution is not blocked in upload foldersCheck for .htaccess file in upload directories with 'php_flag engine off' or 'deny from all', or check nginx config for location blocks preventing PHP execution in /uploads/Affected if No web server restrictions exist to block PHP execution in upload directories
If the BEAF plugin version is 4.6.10 or lower and PHP files exist in the upload directories, the vulnerability is likely present and may have been exploited.
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 dataUpdate the BEAF plugin to the latest patched version immediately. As an interim measure, disable the plugin if not needed, or implement web server-level restrictions to prevent PHP execution in upload directories and remove any already-uploaded malicious files.
Fix this in Ultimate Before After Image Slider \& Gallery
Scoped from the published advisory
- Consultation6.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,968.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-47549 — 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-2025-47549 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