Nasa CoreWordPress extension · Nasatheme
CVE-2025-39507
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 · uneditedImproper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') vulnerability in NasaTheme Nasa Core nasa-core allows PHP Local File Inclusion.This issue affects Nasa Core: from n/a through < 6.4.4.
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 confidenceLocal File Inclusion (LFI) vulnerability in NASA Core WordPress plugin allows attackers to include arbitrary local PHP files due to improper input validation on include/require statements. This can lead to remote code execution if attackers can control or upload files to locations the PHP process can access.
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
Nasa CoreWordPress extension
<= 6.3.2CVSS 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
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/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.
-
Check if NASA Core plugin is installedNavigate to WordPress admin dashboard > Plugins > Installed Plugins. Look for 'Nasa Core' in the list of installed plugins. Alternatively, check the filesystem at /wp-content/plugins/nasa-core/ exists.Affected if The plugin is not found in the plugins directory.
-
Determine installed NASA Core versionIn WordPress admin > Plugins, find 'Nasa Core' and read the version number displayed below the plugin name. Or check the main plugin file (e.g., nasa-core.php) for the 'Version' header in the plugin comments.Affected if The version displayed is 6.3.2 or lower.
-
Verify plugin is activeIn WordPress admin > Plugins, check if 'Nasa Core' shows 'Active' status. LFI only affects the plugin when it is loaded by PHP.Affected if Plugin is active and version is 6.3.2 or lower.
-
Check for suspicious include/require parameters in logsReview web server access logs (Apache/Nginx) for patterns like '?file=../' or '?file=php://' in requests to paths containing 'nasa-core'. Also check for unusual PHP files in the wp-content/uploads/ directory.Affected if Log entries show directory traversal patterns or file inclusion attempts targeting this plugin.
A system is affected if the NASA Core plugin is installed, active, and running version 6.3.2 or lower.
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 · scopedUpgrade NASA Core plugin to version 6.4.4 or later to patch the file inclusion vulnerability. If immediate patching is not feasible, implement web application firewall rules to block directory traversal patterns (e.g., ../) in request parameters.
6.4.4
- 1. Back up your WordPress site database and files before making any changes
- 2. Navigate to Plugins > Installed Plugins in WordPress admin dashboard
- 3. Locate 'Nasa Core' (or 'NasaTheme - Nasa Core') in the plugin list
- 4. If an update is available, click 'Update Now' to upgrade to version 6.4.4
- 5. Alternatively, download version 6.4.4 from a trusted source and upload/install it manually
- 6. After updating, clear any site caches and verify the plugin shows version 6.4.4
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Nasa Core
Scoped from the published advisory
- Consultation2.0 h
- Implementation1.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-39507 — 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-39507 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