CVE-2025-1304

NewsBlogger <= 0.2.5.1 - Authenticated (Subscriber+) Arbitrary File Upload

2025-04-30 15:00
CVE_hunter

Strategic Overview

Status
Patched in 0.2.5.2
Affected Theme
NewsBlogger
Affected Version
<= 0.2.5.1
CVSS
8.8High
Weakness type
CWE-862 · Missing Authorization
CVE
CVE-2025-1304
View all NewsBlogger vulnerabilities

At a glance

CVE-2025-1304 is a high-severity Missing Authorization vulnerability in the NewsBlogger WordPress theme, affecting versions <= 0.2.5.1. It carries a CVSS score of 8.8 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). Exploitation requires an authenticated account at Subscriber level or above. The issue is fixed in version 0.2.5.2; sites on affected versions should update now. Disclosed April 2025, reported by CVE_hunter.

Vulnerability Overview

The NewsBlogger theme for WordPress is vulnerable to arbitrary file uploads due to a missing capability check on the newsblogger_install_and_activate_plugin() function in all versions up to, and including, 0.2.5.1. This makes it possible for authenticated attackers, with subscriber-level access and above, to upload arbitrary files on the affected site's server which may make remote code execution possible.

Technical Analysis

The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no interaction from a victim user. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.

CWE-862: Missing Authorization

NewsBlogger <= 0.2.5.1 carries this weakness at newsblogger_install_and_activate_plugin(), and reaching it takes an account at Subscriber level or above. A missing authorization check means a function is reachable by anyone who can reach the endpoint, because the code never asks whether the caller is allowed to perform the action.

Any user who can reach the endpoint gets to run an action reserved for higher-privileged roles, from reading protected data to changing settings or content. For NewsBlogger the fix is 0.2.5.2: builds <= 0.2.5.1 are affected, anything from 0.2.5.2 onward is not.

Remediation

Update to version 0.2.5.2, or a newer patched version

How does WordSec protect against this?

Because it turns on account access, WordSec's login security is the relevant layer: role-based two-factor, captcha and brute-force limits raise the cost of getting the account this needs. None of that substitutes for the fix: NewsBlogger 0.2.5.2 closes this, and updating the theme is the step that ends it.

  • Login Security
  • Alerts

External References

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C