LiveActive security incident?Get immediate response
CVE Record

CVE-2025-22773: WordPress Htaccess File Editor <= 1.0.19 - Broken Authentication vulnerability

Insertion of Sensitive Information into Externally-Accessible File or Directory vulnerability in WP Chill Htaccess File Editor htaccess-file-editor allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Htaccess File Editor: from n/a through <= 1.0.19.

MediumCVSS 5.3Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2025-22773 affects the WordPress Htaccess File Editor plugin through version 1.0.19. The issue may expose sensitive information in a web-accessible location because access control is incorrectly configured. Impact is confidentiality-only and rated medium in the source data.

Executive priority

Treat as a moderate WordPress hygiene issue. Prioritize externally facing WordPress sites, especially where configuration files may contain sensitive data. It does not currently warrant emergency response based on the provided evidence.

Technical view

The CVE describes CWE-538, insertion of sensitive information into an externally accessible file or directory, in WP Chill Htaccess File Editor. CVSS 3.1 is 5.3 with network attack vector, low complexity, no privileges, no user interaction, and low confidentiality impact.

Likely exposure

Exposure is likely limited to WordPress sites that have the Htaccess File Editor plugin installed at version 1.0.19 or earlier. The source bundle does not identify other affected products or environments.

Exploitation context

The CVE is not listed as KEV in the provided bundle, and no cited source states active exploitation. The scoring indicates remote unauthenticated reachability, but available evidence only supports limited information disclosure, not integrity or availability impact.

Researcher notes

Public details are sparse. The source data names broken authentication/access control and CWE-538, but does not provide a patch version, proof of exploitation, or precise vulnerable endpoint. Avoid assuming broader compromise capability without vendor detail.

Mitigation direction

  • Inventory WordPress sites for Htaccess File Editor and record installed versions.
  • Check WP Chill, WordPress plugin, or Patchstack guidance for a fixed version or workaround.
  • Update the plugin if a vendor-supported fixed release is available.
  • Disable or remove the plugin where it is not business-critical.
  • Review web-accessible files for unintended sensitive information exposure.

Validation and detection

  • Confirm whether Htaccess File Editor is installed and version is 1.0.19 or earlier.
  • Review WordPress and web server logs for unusual unauthenticated access to exposed files.
  • Validate that sensitive configuration data is not stored in externally accessible locations.
  • Check whether vendor guidance has been applied across all affected sites.
Prepared
Confidence
medium
Sources
3

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-538: 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.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2025-22773 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
Medium
CVSS
5.3 (3.1)
Known Exploited
No
Published

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

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
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.

ScoreVersionSeverityVectorExploitImpactSource
5.3CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N3.91.4Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

5.3Medium
CVSS 3.1 vector shape for CVE-2025-22773Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

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 ChillHtaccess File Editorhtaccess-file-editor, 0unaffected
Weakness

CWE details

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

CWE-538 · source CWE mapping

Insertion of Sensitive Information into Externally-Accessible File or Directory

Insertion of Sensitive Information into Externally-Accessible File or Directory represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.