VulnerabilityPublished 2 Dec 2025

CVE-2025-12630: Upload.am (WordPress plugin) · Missing Authorization

Affects Upload.am (WordPress plugin)Source CVE Database V5

Not known to be exploited · CVSS 4.9 Medium · fixed in 1.0.1 : update Upload.am (WordPress plugin) when convenient.

Data as of 26 Oct 2026, 09:15 UTC

CVSS 3.1 base score

4.9Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.2% chance of exploitation in 30 days – higher than 18% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 1.0.1

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

Attack Vector: Network
Attack Complexity: Low
Privileges Required: High
User Interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: None
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: High: The attacker is authorized with (i.e., requires) privileges that provide significant (e.g., administrative) control over the vulnerable component that could affect component-wide settings and files.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 2 Dec 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
Upload.am	Affected =0	Fixed in–

AI-suggested

1. Immediately update the Upload.am WordPress plugin to version 1.0.1 or later once available to ensure the missing authorization check is implemented. 2. Audit all WordPress user roles and permissions to ensure that contributor accounts are assigned only to trusted users and that their privileges are minimized. 3. Implement strict role-based access control (RBAC) policies to limit the number of users with contributor or higher privileges. 4. Monitor AJAX request logs for unusual access patterns or attempts to access site options by contributor accounts. 5. Employ Web Application Firewalls (WAFs) with custom rules to detect and block unauthorized AJAX requests targeting the vulnerable endpoints. 6. Regularly review and harden WordPress security configurations, including disabling unnecessary plugins and limiting plugin installations to trusted sources. 7. Educate site administrators and content contributors about the risks of privilege misuse and encourage reporting of suspicious activity. 8. Consider implementing multi-factor authentication (MFA) for all privileged accounts to reduce the risk of compromised credentials being exploited.

Description

The Upload.am WordPress plugin before 1.0.1 is vulnerable to arbitrary option disclosure due to a missing capability check on its AJAX request handler, allowing users such as contributor to view site options.

Impact

For European organizations, this vulnerability poses a risk primarily to the confidentiality of WordPress site configurations. Organizations using the Upload.am plugin on their WordPress installations could have sensitive site options exposed to users with contributor-level access, which is often granted to content creators or editors. This exposure could lead to information leakage about site settings, plugin configurations, or other sensitive data that could be used to facilitate further attacks such as privilege escalation, targeted phishing, or site defacement. While the vulnerability does not impact integrity or availability directly, the confidentiality breach can undermine trust and lead to compliance issues under GDPR if personal or sensitive data configurations are exposed. European organizations with active web content management and development teams that assign contributor roles are particularly at risk. The lack of known exploits reduces immediate risk but does not eliminate the threat, especially as attackers may develop exploits given the public disclosure. The impact is more pronounced in sectors with high reliance on WordPress for public-facing or internal sites, such as media, education, and government agencies.

CWE-862Missing Authorization (opens in a new tab)
Class weaknessLikelihood of exploit: HighCWE Top 25 (2025): #4OWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
The product does not perform an authorization check when an actor attempts to access a resource or perform an action.
Architecture and Design
Divide the product into anonymous, normal, privileged, and administrative areas. Reduce the attack surface by carefully mapping roles with data and functionality. Use role-based access control (RBAC) to enforce the roles at the appropriate boundaries.
Architecture and Design
Ensure that access control checks are performed related to the business logic. These checks may be different than the access control checks that are applied to more generic resources such as files, connections, processes, memory, and database records.
Architecture and Design · Libraries or Frameworks
Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
OWASP Cheat Sheets
Authorization (opens in a new tab)
OWASP ASVS 4.0.3
V8.3.8 (opens in a new tab)
V13.4.2 (opens in a new tab)
V7.2.2 (opens in a new tab)
Attack patterns
Exploitation of Thunderbolt Protection Flaws (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

wpscan.com/vulnerability/531537f1-5547-4b0f-9e11-3f8a0b2589f5/ (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 2 Dec 2025, 16:13 UTC

WeaknessesCWE-862

Technical details

References

Community reviews

Related threats