VulnTitan VulnTitan Security command center
Plugin Vulnerability Hub
Plugin 1 known issue Latest disclosed Oct 03, 2025

Majestic Before After Image Vulnerabilities

Review known vulnerability records for the WordPress plugin Majestic Before After Image (`majestic-before-after-image`), including severity, CVE references, affected versions, and patch status.

Recent tracked CVEs on this page include CVE-2025-9030, so operators can jump from disclosure to patch validation without scanning the full feed first.

View on WordPress.org Back to Feed
Known Records
1
High or Critical
0
Patch Coverage
100%
Last Updated
Oct 04, 2025
Related Security Guides

Use these guides while reviewing Majestic Before After Image fixes

Pair this plugin vulnerability hub with practical WordPress hardening, scanner, and patch workflow guidance.

Hardening
WordPress hardening checklist for exposed plugins

Review patch cadence, privileged access, XML-RPC exposure, backups, and monitoring controls.
Plugin Security
WordPress plugin security basics for patch decisions

Use ownership, update testing, least privilege, and removal criteria to reduce plugin risk.
Scanning
WordPress vulnerability scanner buyer's guide

Compare scanner coverage for plugin CVEs, version detection, alert noise, and remediation workflow.
Patch Decision Workflow

How to prioritize Majestic Before After Image remediation

Use the hub as a decision layer before opening individual records: confirm whether the issue has a CVE, whether a fixed version exists, and whether the affected range overlaps production installs.

Search-Ready Records
1
1. Match the Package
Confirm the installed WordPress plugin slug is majestic-before-after-image before acting on any CVE from this cluster.
2. Sort by Severity
Start with 0 high or critical records, then review medium and unrated findings with public references.
3. Check Patch Evidence
1 record include a patch path; verify compatibility before closing the finding.
4. Monitor Gaps
0 records still lack a listed fixed release, so keep this hub in the review queue.
High-Signal Remediation Targets
CVE-2025-9030 Medium
Stored Cross-Site Scripting remediation for Majestic Before After Image

Affected range: Versions up to 2.0.2. Fixed version: 2.0.3.

Priority CVE Quick Links

Fast paths into Majestic Before After Image CVE reports

Start with the highest-signal CVE records for this WordPress plugin before scanning the full vulnerability feed.

Indexed CVEs
1
Tracked CVE Issue Type Affected Versions Fixed Version CVSS
CVE-2025-9030
Majestic Before After Image <= 2.0.2 - Authenticated (Contributor+) Stored Cross-Sit...
 Stored Cross-Site Scripting Versions up to 2.0.2 2.0.3 CVSS 5.4
CVE-2025-9030 Medium 2.0.3
CVE-2025-9030 Majestic Before After Image Stored Cross-Site Scripting

Majestic Before After Image <= 2.0.2 - Authenticated (Contributor+) Stored Cross-Site Scripting

Coverage Snapshot

What this page helps you verify fast

This hub clusters tracked records for Majestic Before After Image so operators can confirm whether a disclosed issue maps to the installed slug, version range, and patch path.

Patch Visibility
1 record include a published patch path, leaving 0 with no listed safe release yet.
Severity Mix
0 critical and 0 high severity findings.
Recent CVEs
CVE-2025-9030
Reference Workflow
Jump from the hub into the full report when you need remediation notes, exploit context, CVSS vectors, or source references.
Triage First

Open the records most likely to drive action

These recent records surface the CVE strings, patch cues, and direct report links most operators need first.

Known Vulnerabilities

Reports for Majestic Before After Image

Sorted by latest disclosure date so newly published issues surface first.

Plugin Medium Patched: Yes CVE-2025-9030
CVE-2025-9030: Majestic Before After Image <= 2.0.2 - Authenticated (Contributor+) Stored Cross-Site Scripting

The Majestic Before After Image plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'before_label' and 'after_label' parameters in versions less than, or equal to, 2.0.1 due to insufficient input sanitization and output escaping. This makes it possible for a...

Published
Oct 03, 2025
Patched Release
2.0.3
Affected Versions
Versions up to 2.0.2
Next Step
Update to 2.0.3 or newer if supported.
Review CVE-2025-9030 fixed version details Open CVE Reference