Internal-service access via unauthenticated server-side requests
Published Jan 31, 2025 · Updated May 11, 2026
SSRF in BrandExponents Oshine Modules before 3.3.8 allows remote attackers to send requests from the WordPress server. Patchstack and the vendor do not identify the affected handler or explain how attacker-controlled input reaches the outbound request. No authentication is required, but the additional conditions are undisclosed; exploitation lets the server contact arbitrary destinations and expose or modify reachable internal-service data.
Summary
What happened
SSRF in BrandExponents Oshine Modules before 3.3.8 allows remote attackers to send requests from the WordPress server. Patchstack and the vendor do not identify the affected handler or explain how attacker-controlled input reaches the outbound request. No authentication is required, but the additional conditions are undisclosed; exploitation lets the server contact arbitrary destinations and expose or modify reachable internal-service data.
The record
- CVE
- CVE-2024-44055
- Published
- Jan 31, 2025
- Updated
- May 11, 2026
- Vendor
- BrandExponents
- Product
- Oshine Modules
- Classifications
- CWE-918, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 31, 2025CVE publishedPublication date reported by the CVE source.
- May 11, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <=3.3.8 changes=[{"at":"3.3.8","status":"unaffected"}]
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo