LiveActive security incident?Get immediate response
CVE Record

CVE-2023-27812: bloofox v0.5.2 was discovered to contain an arbitrary file deletion vulnerability via the delete_file() fun...

bloofox v0.5.2 was discovered to contain an arbitrary file deletion vulnerability via the delete_file() function.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2023-27812 reports that bloofox v0.5.2 can delete arbitrary files through its delete_file() function. In business terms, a successful attack could remove application or system files, causing outages or data loss. Public data does not provide a CVSS score, confirmed patch, or evidence of active exploitation.

Executive priority

Treat as a targeted remediation item, not an emergency based on current evidence. Prioritize if bloofox v0.5.2 is internet-facing, business-critical, or handles important content files. Lack of patch and severity data means verification should come first.

Technical view

The CVE record describes an arbitrary file deletion flaw in bloofox v0.5.2 via delete_file(). The published metadata has no CWE, CVSS, CPE, or detailed affected-product mapping. The referenced GitHub issue appears to be the main technical disclosure, but remediation details are not established in the provided sources.

Likely exposure

Organizations are likely exposed only if they run bloofox v0.5.2 or code derived from the referenced PHP CMS project. Exposure cannot be reliably confirmed from CPE data because the CVE record lists no normalized affected product identifiers.

Exploitation context

The CVE is not listed as CISA KEV in the provided bundle. A public GitHub issue is referenced, so technical details may be publicly accessible. The sources do not confirm active exploitation, weaponized exploit use, or exploitation in the wild.

Researcher notes

The record is sparse and lacks CVSS, CWE, CPE, and vendor advisory detail. Analysis should start with the CVE record and referenced GitHub issue. Avoid assuming broader product impact beyond bloofox v0.5.2 unless confirmed by project evidence.

Mitigation direction

  • Identify any deployed bloofox v0.5.2 instances or derived codebases.
  • Review vendor or project guidance for fixed versions or official mitigations.
  • Restrict administrative or file-management functionality to trusted users only.
  • Ensure reliable backups exist for application and content files.
  • Monitor for unexpected file deletions in application directories.

Validation and detection

  • Check software inventory for bloofox v0.5.2 references.
  • Review code for use of the delete_file() function.
  • Confirm whether access controls protect file deletion features.
  • Inspect logs for unusual deletion events or missing files.
  • Track the referenced GitHub issue and vendor site for updates.
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.

description · low confidence lookup

File access behavior lookup

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.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2023-27812 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
Unknown
CVSS
Not scored
Known Exploited
No
Published
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.

0CVSS vectors
3Timeline events
1ADP providers
4Source links

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CVECVE Program Container

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

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