LiveActive security incident?Get immediate response
CVE Record

CVE-2025-31421: WordPress Srbtranslatin plugin <= 3.2.0 - Sensitive Data Exposure vulnerability

Insertion of Sensitive Information into Externally-Accessible File or Directory vulnerability in Oblak Studio Srbtranslatin srbtranslatin allows Retrieve Embedded Sensitive Data.This issue affects Srbtranslatin: from n/a through <= 3.2.0.

MediumCVSS 5.8Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2025-31421 affects the WordPress Srbtranslatin plugin through version 3.2.0. The reported issue can expose sensitive embedded information from an externally accessible location. The impact is limited to confidentiality, but it is remotely reachable without authentication or user interaction according to the CVSS vector.

Executive priority

Treat this as a moderate-priority WordPress plugin exposure issue. Prioritize externally reachable production sites, especially where WordPress may hold customer, operational, or credential-adjacent data. Escalate if sensitive data is confirmed exposed.

Technical view

The vulnerability is classified as CWE-538: insertion of sensitive information into an externally accessible file or directory. Sources describe affected Srbtranslatin versions as up to 3.2.0. CVSS 3.1 is 5.8 with network attack vector, low complexity, no privileges, no user interaction, scope changed, and low confidentiality impact.

Likely exposure

Exposure is likely limited to WordPress sites that have the Srbtranslatin plugin installed at version 3.2.0 or earlier. The bundle does not identify affected hosted services, CPEs, or a confirmed fixed version.

Exploitation context

The source bundle does not show CISA KEV listing or cite active exploitation. The CVSS vector indicates the issue is remotely reachable without authentication, but only low confidentiality impact is stated.

Researcher notes

Evidence is limited to CVE and Patchstack-style vulnerability metadata. No exploit details, active exploitation evidence, patch version, or vendor advisory is included in the bundle. Validate exposure conservatively and avoid assuming all WordPress installations are affected.

Mitigation direction

  • Inventory WordPress sites for the Srbtranslatin plugin and record installed versions.
  • If version is 3.2.0 or earlier, check vendor and Patchstack guidance immediately.
  • Disable or remove the plugin where business need is low and no fixed version is available.
  • Restrict public exposure of unnecessary plugin files through standard WordPress hardening controls.
  • Monitor vendor channels for a confirmed fixed release or replacement guidance.

Validation and detection

  • Confirm whether Srbtranslatin is installed, active, or present but inactive on each WordPress site.
  • Verify the installed plugin version against the affected range through 3.2.0.
  • Review web server logs for unusual requests targeting Srbtranslatin plugin resources.
  • Check whether sensitive data is present in publicly reachable plugin-generated files.
  • Document remediation status for each affected WordPress instance.
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-31421 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.8 (3.1)
Known Exploited
No
Published

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

Vulnerability scoring details

Base CVSS 3.1 score

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

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/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
Oblak StudioSrbtranslatinsrbtranslatin, 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.