🟡 CVE-2025-4021: A vulnerability was found in c... 🟡 CVE-2025-4020: A vulnerability was found in P... 🟡 CVE-2025-32472: The multiScan and picoScan are... 🟡 CVE-2025-4019: A vulnerability, which was cla... 🟡 CVE-2025-4018: A vulnerability, which was cla... 🟡 CVE-2025-4017: A vulnerability classified as ... 🟡 CVE-2025-4016: A vulnerability classified as ... 🟡 CVE-2025-4015: A vulnerability was found in 2... 🟡 CVE-2025-4014: A vulnerability was found in P... 🔥 CVE-2025-3200: An unauthenticated remote atta... 🟡 CVE-2025-4013: A vulnerability was found in P... 🟡 CVE-2025-4012: A vulnerability was found in p... 🟡 CVE-2025-4011: A vulnerability has been found... ⚠️ CVE-2025-42598: Multiple SEIKO EPSON printer d... 🟡 CVE-2025-39367: Missing Authorization vulnerab... 🟢 CVE-2025-32471: The device’s passwords have no... ⚠️ CVE-2025-32470: A remote unauthenticated attac... ⚠️ CVE-2025-4007: A vulnerability classified as ... ⚠️ CVE-2025-22235: EndpointRequest.to() creates a... 🟡 CVE-2025-4006: A vulnerability classified as ... 🟡 CVE-2025-4005: A vulnerability was found in P... 🟡 CVE-2025-4004: A vulnerability was found in P... 🟡 CVE-2025-4003: A vulnerability was found in R... 🟡 CVE-2025-4002: A vulnerability was found in R... 🟡 CVE-2025-4001: A vulnerability has been found... 🟡 CVE-2025-4000: A vulnerability, which was cla... 🟡 CVE-2025-3999: A vulnerability, which was cla... 🟡 CVE-2025-3998: A vulnerability classified as ... 🟡 CVE-2025-3997: A vulnerability classified as ... 🟡 CVE-2025-3996: A vulnerability was found in T... 🟡 CVE-2025-3706: The eHRMS from 104 Corporation... 🟡 CVE-2025-3995: A vulnerability was found in T... 🟡 CVE-2025-3994: A vulnerability was found in T... ⚠️ CVE-2025-3993: A vulnerability was found in T... ⚠️ CVE-2025-3992: A vulnerability has been found... ⚠️ CVE-2025-3991: A vulnerability, which was cla... 🟡 CVE-2025-31144: Quick Agent V3 and Quick Agent... ⚠️ CVE-2025-27937: Quick Agent V3 and Quick Agent... 🔥 CVE-2025-26692: Quick Agent V3 and Quick Agent... ⚠️ CVE-2025-3990: A vulnerability, which was cla... ⚠️ CVE-2025-3989: A vulnerability classified as ... 🟡 CVE-2025-46690: Ververica Platform 2.14.0 allo... 🟡 CVE-2025-46689: Ververica Platform 2.14.0 cont... ⚠️ CVE-2025-3988: A vulnerability classified as ... 🟡 CVE-2025-3987: A vulnerability was found in T... 🟡 CVE-2025-3986: A vulnerability was found in A... 🟡 CVE-2025-3985: A vulnerability was found in A... 🟡 CVE-2025-46688: quickjs-ng through 0.9.0 has a... 🟡 CVE-2025-46687: quickjs-ng through 0.9.0 has a... 🟢 CVE-2025-3984: A vulnerability was found in A... 🟡 CVE-2025-3983: A vulnerability has been found... 🟡 CVE-2025-3982: A vulnerability, which was cla... 🟡 CVE-2025-3981: A vulnerability, which was cla... 🟢 CVE-2025-2866: Improper Verification of Crypt... 🟡 CVE-2025-3980: A vulnerability classified as ... 🟡 CVE-2025-3979: A vulnerability classified as ... 🟡 CVE-2025-3978: A vulnerability was found in d... 🟡 CVE-2025-3977: A vulnerability was found in i... ⚠️ CVE-2025-46657: Karaz Karazal through 2025-04-... 🟡 CVE-2025-3976: A vulnerability was found in P... 🟡 CVE-2025-3975: A vulnerability was found in S... 🟡 CVE-2025-3974: A vulnerability has been found... 🟡 CVE-2025-3973: A vulnerability, which was cla... 🟡 CVE-2025-3972: A vulnerability, which was cla... 🟡 CVE-2025-3971: A vulnerability classified as ... 🟡 CVE-2025-3970: A vulnerability classified as ... 🟡 CVE-2025-3969: A vulnerability was found in c... 🟡 CVE-2025-3968: A vulnerability was found in c... 🟡 CVE-2025-3967: A vulnerability was found in i... 🟡 CVE-2025-3886: An issue in CatoNetworks CatoC... 🟡 CVE-2025-3966: A vulnerability was found in i... 🟡 CVE-2025-3965: A vulnerability has been found... 🟡 CVE-2025-3964: A vulnerability, which was cla... 🟡 CVE-2025-3963: A vulnerability, which was cla... 🟡 CVE-2024-52888: For an authenticated end-user ... 🟢 CVE-2024-52887: Authenticated end-user may set... 🟡 CVE-2025-3962: A vulnerability classified as ... 🟡 CVE-2025-3961: A vulnerability classified as ... 🟡 CVE-2025-3960: A vulnerability was found in w... 🟡 CVE-2025-3959: A vulnerability was found in w... 🟡 CVE-2025-3958: A vulnerability was found in w... 🟡 CVE-2025-3957: A vulnerability was found in o... 🟡 CVE-2025-3956: A vulnerability has been found... ⚠️ CVE-2025-46580: There is a code-related vulner... ⚠️ CVE-2025-46579: There is a DDE injection vulne... 🟡 CVE-2025-46578: There are SQL injection vulner... 🟡 CVE-2025-46577: There is a SQL injection vulne... 🟡 CVE-2025-46576: There is a Permission Manageme... 🟡 CVE-2025-46575: There is an information disclo... 🟡 CVE-2025-46574: There is an information disclo... 🟢 CVE-2025-46675: In NASA CryptoLib before 1.3.2... 🟢 CVE-2025-46674: NASA CryptoLib before 1.3.2 us... 🟡 CVE-2025-46673: NASA CryptoLib before 1.3.2 do... 🟢 CVE-2025-46672: NASA CryptoLib before 1.3.2 do... 🟡 CVE-2025-3955: A vulnerability, which was cla... 🟢 CVE-2025-46656: python-markdownify (aka markdo... 🟡 CVE-2025-3954: A vulnerability, which was cla... 🟡 CVE-2025-46655: CodiMD through 2.5.4 has a CSP... 🟡 CVE-2025-46654: CodiMD through 2.2.0 has a CSP... 🟢 CVE-2025-46653: Formidable (aka node-formidabl...
PhishWP Plugin: A New Threat to WordPress Security

PhishWP Plugin: A New Threat to WordPress Security

A malicious WordPress plugin named PhishWP has emerged, enabling cybercriminals to transform legitimate websites into phishing traps. Distributed on Russian cybercrime forums, PhishWP allows attackers to create convincing fake payment pages that mimic trusted services like Stripe. These fraudulent interfaces deceive users into entering sensitive information, including credit card details and one-time passwords (OTPs), which are then transmitted to attackers via Telegram in real-time.

PhishWP operates by compromising legitimate WordPress sites or setting up fraudulent ones to host the plugin. Once installed, it replicates trusted payment gateways, creating fake checkout pages that are nearly indistinguishable from authentic ones. This tactic lures unsuspecting users into providing sensitive information, believing they are engaging with a secure, legitimate site.

The plugin's capabilities extend to harvesting 3D Secure authentication codes, a security measure used during online transactions. By capturing these OTPs in real-time, attackers can bypass authentication protocols, facilitating fraudulent transactions while maintaining an appearance of legitimacy.

The emergence of PhishWP underscores the evolving nature of cyber threats targeting WordPress platforms. As we advance into 2025, the WordPress ecosystem faces increasing challenges from sophisticated attacks. Experts predict a rise in AI-powered threats, with vulnerabilities having already increased by 21% in 2024. Hackers are expected to leverage AI to develop more advanced attacks, necessitating heightened security measures.

To safeguard against such threats, WordPress site owners and administrators should consider the following measures:

  • Regularly update WordPress core, themes, and plugins to patch known vulnerabilities.
  • Implement strong, unique passwords and enable two-factor authentication (2FA) to enhance login security.
  • Conduct regular security audits and vulnerability assessments to identify and address potential weaknesses.
  • Utilize reputable security plugins that offer features like malware scanning, firewall protection, and real-time monitoring.
  • Educate users and administrators about phishing tactics and the importance of verifying the authenticity of payment pages and other sensitive interfaces.

By adopting these proactive security measures, WordPress site owners can better protect their platforms and users from emerging threats like PhishWP, ensuring a safer online environment in the evolving digital landscape.

Sources

Back to Posts