LiveActive security incident?Get immediate response
CVE Record

CVE-2021-38360: wp-publications <= 0.0 Local File Include

The wp-publications WordPress plugin is vulnerable to restrictive local file inclusion via the Q_FILE parameter found in the ~/bibtexbrowser.php file which allows attackers to include local zip files and achieve remote code execution, in versions up to and including 0.0.

HighCVSS 8.3Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

This CVE affects the wp-publications WordPress plugin. A flaw in file handling can let an unauthenticated attacker include local zip files through the plugin and potentially reach remote code execution. The source bundle does not name a fixed version or confirmed active exploitation.

Executive priority

Prioritize this as high where wp-publications is installed on public WordPress sites. The business risk is potential server compromise, but urgency depends on confirmed plugin presence because the affected product scope is narrow.

Technical view

CVE-2021-38360 is a CWE-22 local file inclusion issue in wp-publications through the Q_FILE parameter in bibtexbrowser.php. The CVSS 3.1 score is 8.3, with network attack vector, low complexity, no privileges, and no user interaction required. Sources describe versions up to and including 0.0 as affected.

Likely exposure

Exposure is limited to WordPress sites running the wp-publications plugin in the affected version range. The bundle provides no CPEs and only lists version 0.0, so inventory confirmation is important before scoping impact.

Exploitation context

The CVE text says the issue can allow local zip file inclusion and remote code execution. KEV is false, and the provided sources do not show confirmed active exploitation. Treat internet-facing WordPress instances as the main concern.

Researcher notes

Evidence supports an unauthenticated LFI/path traversal class issue tied to Q_FILE in bibtexbrowser.php. The patch state, exploit prevalence, and complete version history are not established in the provided bundle. Avoid assuming broader WordPress exposure without plugin confirmation.

Mitigation direction

  • Identify WordPress sites running the wp-publications plugin.
  • Disable or remove the plugin if it is not business-critical.
  • Check Wordfence and WordPress plugin guidance for any fixed release.
  • Prioritize remediation on internet-facing WordPress sites.
  • Review access controls around WordPress administration and plugin management.

Validation and detection

  • Inventory installed WordPress plugins and confirm wp-publications version presence.
  • Check web logs for requests to bibtexbrowser.php involving Q_FILE.
  • Compare local plugin code with the referenced bibtexbrowser.php source location.
  • Confirm whether any vendor or Wordfence update supersedes the affected version.
  • Document exposed sites, plugin status, and remediation decisions.
Prepared
Confidence
medium
Sources
4

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 · medium confidence lookup

CWE-22: File access and web shell behavior lookup

File traversal and upload weaknesses can lead teams to review file, web shell, execution, and collection telemetry. 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.

Open ATT&CK lookup
description · low confidence lookup

Execution behavior lookup

The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2021-38360 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
8.3 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:L

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

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
0Timeline events
0ADP providers
3Source 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.

ScoreVersionSeverityVectorExploitImpactSource
8.3CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:L3.93.7Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

8.3High
CVSS 3.1 vector shape for CVE-2021-38360Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:L

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
wp-publicationswp-publications0.0Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-22 · source CWE mapping

Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')

Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.