LiveActive security incident?Get immediate response
CVE Record

CVE-2025-55710: WordPress TaxoPress Plugin <= 3.37.2 - Sensitive Data Exposure Vulnerability

Insertion of Sensitive Information Into Sent Data vulnerability in Steve Burge TaxoPress simple-tags allows Retrieve Embedded Sensitive Data.This issue affects TaxoPress: from n/a through <= 3.37.2.

MediumCVSS 4.3Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2025-55710 is a medium-severity sensitive data exposure issue in the WordPress TaxoPress plugin, also identified as simple-tags, affecting versions through 3.37.2. A logged-in attacker could retrieve limited sensitive information sent by the plugin. The sources do not show active exploitation or a named fixed version.

Executive priority

Treat this as a moderate remediation item. It does not justify emergency outage response based on current evidence, but affected internet-facing WordPress sites with many logins should be prioritized for version verification and vendor-guided remediation.

Technical view

The issue is classified as CWE-201, insertion of sensitive information into sent data. CVSS 3.1 is 4.3: network exploitable, low complexity, low privileges required, no user interaction, unchanged scope, low confidentiality impact, and no integrity or availability impact.

Likely exposure

Exposure is most likely on WordPress sites running TaxoPress/simple-tags version 3.37.2 or earlier, especially where untrusted or numerous users can authenticate. Anonymous-only threat exposure is not supported by the CVSS vector because privileges are required.

Exploitation context

The provided bundle does not identify active exploitation, CISA KEV listing, public exploit code, or indicators of compromise. The risk is practical for authenticated misuse, but the documented impact is limited to confidentiality with no stated data modification or outage effect.

Researcher notes

Evidence is sparse. The record names TaxoPress/simple-tags through 3.37.2 and CWE-201, but does not describe the exposed data, endpoint, required role, exploit chain, or fixed version. Avoid assuming broader impact beyond low confidentiality exposure for authenticated users.

Mitigation direction

  • Inventory WordPress sites for TaxoPress/simple-tags and record installed versions.
  • Check vendor and Patchstack guidance for a fixed release or official mitigation.
  • Update affected installations when a vendor-supported fixed version is confirmed.
  • Limit plugin access to trusted authenticated users where feasible.
  • Disable the plugin temporarily on high-sensitivity sites if no fix is available.

Validation and detection

  • Confirm whether TaxoPress/simple-tags is installed on each WordPress site.
  • Verify installed versions are not 3.37.2 or earlier.
  • Review authenticated user roles and remove unnecessary accounts.
  • Check WordPress and web logs for unusual authenticated plugin access.
  • Monitor the CVE record and Patchstack entry for updated remediation details.
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 · medium confidence lookup

CWE-201: Information exposure and cloud metadata lookup

Information exposure and SSRF weaknesses can make discovery, cloud metadata, and credential material review relevant. 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-55710 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
4.3 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:L/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
4.3CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N2.81.4Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

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

Vector: CVSS:3.1/AV:N/AC:L/PR:L/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
Steve BurgeTaxoPresssimple-tags, 0unaffected
Weakness

CWE details

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

CWE-201 · source CWE mapping

Insertion of Sensitive Information Into Sent Data

Insertion of Sensitive Information Into Sent Data represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.