Security readout for executives and security teams
Plain-English summary
This WordPress plugin flaw could let an unauthenticated internet user download files the site should not expose. The main business risk is confidentiality loss from websites running Premium Age Verification / Restriction for WordPress version 3.0.2 or older.
Executive priority
High priority for any public WordPress site using this plugin, because exploitation requires no login or user interaction and can expose confidential files. Urgency depends on whether the plugin is installed.
Technical view
CVE-2025-49403 is an unauthenticated arbitrary file download issue in AA-Team's Premium Age Verification / Restriction for WordPress plugin, slug age-restriction, reported for versions <= 3.0.2. CVSS 3.1 is 7.5 with high confidentiality impact only.
Likely exposure
Exposure is limited to WordPress sites with the affected plugin installed and reachable. The bundle does not identify affected CPEs, hosting platforms, or a confirmed fixed version.
Exploitation context
The source bundle marks KEV as false and provides no cited evidence of active exploitation. Treat this as remotely exploitable due to AV:N, AC:L, PR:N, and UI:N, but do not assume exploitation in the wild.
Researcher notes
The evidence is sparse: affected versions are stated as <= 3.0.2, while the affected record also lists versions as n/a and defaultStatus unaffected. No exploit status, fixed version, or workaround is included in the bundle.
Mitigation direction
Inventory WordPress sites for the age-restriction plugin and installed version.
Check Patchstack, CVE, and vendor guidance for a fixed release or official mitigation.
Disable or remove the plugin where it is not business-critical.
Prioritize remediation for public WordPress sites and sites holding sensitive data.
Validation and detection
Confirm whether Premium Age Verification / Restriction for WordPress is installed.
Record the installed plugin version and compare it with <= 3.0.2.
Review web server and WordPress logs for unusual file access indicators.
Verify remediation by confirming the plugin is updated, disabled, or removed.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-98: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The CVE wording references file access or upload behavior, so file telemetry and web shell review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
1CVSS vectors
3Timeline events
0ADP providers
2Source links
CVSS vector scores
1 official score
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-98 · source CWE mapping
Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion')
Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.