CVE-2025-12954VulnerabilityPublished 3 Dec 2025Updated 9 Jan 2026

CVE-2025-12954: Timetable and Event Schedule by MotoPress (WordPress plugin) · Insecure Direct Object Reference

Affects Timetable and Event Schedule by MotoPress (WordPress plugin)Source CVE Database V5

Not known to be exploited · CVSS 2.7 Low · fixed in 2.4.16 : update Timetable and Event Schedule by MotoPress (WordPress plugin) when convenient.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.1 base score

2.7Low

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

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

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

Attack Vector: Network
Attack Complexity: Low
Privileges Required: High
User Interaction: None
Scope: Unchanged
Confidentiality: Low
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: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
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 3 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 2026-10-26.

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
Timetable and Event Schedule by MotoPress	Affected =0	Fixed in–

AI-suggested

To mitigate CVE-2025-12954, European organizations should immediately upgrade the Timetable and Event Schedule by MotoPress plugin to version 2.4.16 or later, where the authorization checks have been properly implemented. Additionally, organizations should audit user roles and permissions within WordPress to ensure that Contributor-level users have minimal access and that sensitive event data is not exposed unnecessarily. Implementing the principle of least privilege by restricting Contributor roles or using custom roles with tailored permissions can reduce risk. Monitoring and logging duplication actions in the plugin can help detect suspicious activity. If upgrading is not immediately feasible, consider temporarily restricting event duplication functionality to higher-privileged roles or disabling the plugin if event duplication is not critical. Regularly review and update WordPress plugins and themes to avoid similar vulnerabilities. Finally, educate administrators and users about the risks of privilege escalation and unauthorized data access within WordPress environments.

Description

The Timetable and Event Schedule by MotoPress WordPress plugin before 2.4.16 does not verify a user has access to a specific event when duplicating, leading to arbitrary event disclosure when to users with a role as low as Contributor.

Impact

For European organizations, the primary impact of CVE-2025-12954 is the unauthorized disclosure of event-related information within WordPress sites using the affected plugin. While the confidentiality breach may seem limited, event data could include sensitive scheduling information, internal meetings, or customer-related events, potentially leading to privacy violations or leakage of business-sensitive information. Organizations relying on this plugin for public-facing or internal event management could face reputational damage or compliance issues, especially under GDPR if personal data is involved. The vulnerability does not allow modification or deletion of data, nor does it affect system availability, limiting the scope of damage. However, attackers with Contributor-level access—often granted to less trusted users or external collaborators—could leverage this flaw to gain insights into restricted events, which might be used for social engineering or further attacks. The risk is higher in environments where event data is confidential or strategically important. Since the plugin is popular among WordPress users, organizations in sectors such as education, event management, and corporate communications across Europe should be vigilant.

CWE-639Authorization Bypass Through User-Controlled Key (opens in a new tab)
Base weaknessLikelihood of exploit: HighCWE Top 25 (2025): #24OWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
The system's authorization functionality does not prevent one user from gaining access to another user's data or record by modifying the key value identifying the data.
Architecture and Design
For each and every data access, ensure that the user has sufficient privilege to access the record that is being requested.
Architecture and Design · Implementation
Make sure that the key that is used in the lookup of a specific user's record is not controllable externally by the user or that any tampering can be detected.
Architecture and Design
Use encryption in order to make it more difficult to guess other legitimate values of the key or associate a digital signature with the key so that the server can verify that there has been no tampering.
OWASP Cheat Sheets
Access Control (opens in a new tab)
Authorization Testing Automation (opens in a new tab)
Cross-Site Request Forgery Prevention (opens in a new tab)
Insecure Direct Object Reference Prevention (opens in a new tab)
Authorization (opens in a new tab)
OWASP ASVS 4.0.3
V4.1.2 (opens in a new tab)
V4.2.1 (opens in a new tab)
V8.3.8 (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

wpscan.com/vulnerability/f15dd1ca-aa40-4d3b-9625-e3ace744374d/ (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 9 Jan 2026, 20:51 UTC

WeaknessesCWE-639

Technical details

References

Community reviews

Related threats