LiveActive security incident?Get immediate response
CVE Record

CVE-2025-53560: WordPress Noisa theme <= 2.6.0 - PHP Object Injection Vulnerability

Deserialization of Untrusted Data vulnerability in rascals Noisa noisa allows Object Injection.This issue affects Noisa: from n/a through <= 2.6.0.

HighCVSS 8.8Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2025-53560 is a high-severity PHP object injection issue in the WordPress Noisa theme through version 2.6.0. A successful attack could affect confidentiality, integrity, and availability. The cited data shows low attack complexity but requires low privileges; it does not show confirmed active exploitation.

Executive priority

Treat this as a near-term remediation item for any public WordPress site running Noisa. The business risk is meaningful because the maximum stated impact covers data disclosure, content or system modification, and service disruption. Urgency depends on whether Noisa is deployed and whether low-privileged accounts exist.

Technical view

The issue is CWE-502 deserialization of untrusted data in rascals Noisa. CVSS 3.1 is 8.8 with network attack vector, low complexity, low privileges required, no user interaction, unchanged scope, and high CIA impact. The bundle does not identify a patched version or vendor mitigation.

Likely exposure

Exposure is limited to WordPress sites using the Noisa theme at version 2.6.0 or earlier. Risk is higher where low-privileged WordPress accounts exist or are easy to obtain. Sites not using Noisa are not indicated as affected by the provided sources.

Exploitation context

The CVE is not listed as KEV in the provided bundle, and no cited source confirms active exploitation. The CVSS vector indicates an attacker needs network access and low privileges, with no user interaction required. Public exploit details are not included in the provided evidence.

Researcher notes

Evidence is sufficient for affected product, weakness class, affected range, and CVSS. Evidence is incomplete for exploit availability, patch version, vulnerable code path, and concrete detection indicators. Do not assume unauthenticated exploitation; the supplied vector states PR:L.

Mitigation direction

  • Inventory WordPress sites for the Noisa theme and record installed versions.
  • Review the CVE and Patchstack entry for vendor-confirmed remediation guidance.
  • Prioritize replacing or disabling Noisa installations at version 2.6.0 or earlier if no fix is available.
  • Reduce unnecessary low-privileged WordPress accounts on affected sites.
  • Monitor affected sites for unexpected account, file, or theme changes.

Validation and detection

  • Confirm whether each WordPress site has Noisa installed and enabled.
  • Compare installed Noisa versions against the affected range through 2.6.0.
  • Check whether any vendor or Patchstack update is available before applying changes.
  • Review WordPress user roles for unnecessary low-privileged access.
  • Inspect application logs for suspicious authenticated activity around 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 · medium confidence lookup

CWE-502: Code execution behavior lookup

Code execution and unsafe deserialization weaknesses often justify reviewing execution behavior and process 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
cve · low confidence lookup

CVE-2025-53560 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.8 (3.1)
Known Exploited
No
Published

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

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
8.8CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H2.85.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

8.8High
CVSS 3.1 vector shape for CVE-2025-53560Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

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
rascalsNoisanoisa, 0unaffected
Weakness

CWE details

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

CWE-502 · source CWE mapping

Deserialization of Untrusted Data

Deserialization of Untrusted Data represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.